Re: [microblaze-uclinux] [PATCH 04/56] microblaze_v2: Open firmware files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, May 7, 2008 at 12:40 PM, Michal Simek <monstr@xxxxxxxxx> wrote:
> Hi Steve,
>
>  you are right. Microblaze don't need CONFIG_PPC_something but
>  I keep this in files because it will be easier to move this to better place.
>  I wanted to sort what Microblaze don't use.
>
>  I need to talk with people from sparc and powerpc what we can move and where.
>  I see the best way to push these files to microblaze/kernel/ and then sychronize
>  them with one patch - all archs together.

I would disagree.  I think its better to push (and get merged) patches
to move the files first; then add microblaze on top of that.  You can
start getting stuff merged piecemeal that way instead of relying on
getting your entire patch series merged at once.

However, that's just my opinion, others may look at it differently.

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Kernel Newbies]     [x86 Platform Driver]     [Netdev]     [Linux Wireless]     [Netfilter]     [Bugtraq]     [Linux Filesystems]     [Yosemite Discussion]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]

  Powered by Linux