[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <480FA235.8000203@seznam.cz>
Date: Wed, 23 Apr 2008 22:55:17 +0200
From: Michal Simek <monstr@...nam.cz>
To: Arnd Bergmann <arnd@...db.de>
Cc: Paul Mackerras <paulus@...ba.org>, benh@...nel.crashing.org,
Stephen Neuendorffer <stephen.neuendorffer@...inx.com>,
John Williams <john.williams@...alogix.com>,
jwboyer@...ux.vnet.ibm.com, John Linn <John.Linn@...inx.com>,
git-dev@...inx.com, Grant Likely <grant.likely@...retlab.ca>,
git@...inx.com, microblaze-uclinux@...e.uq.edu.au,
linux-kernel@...r.kernel.org
Subject: Re: Microblaze Linux release
Hi all,
I update Microblaze kernel to latest Linus tree. I fixed some problems which
come with it.
Regards,
Michal
>>> One more reason for the microblaze kernel to base on top of linux-next
>>> instead of mainline.
>> For me is not difficult to use lmb from microblaze/mm or from lib if the files
>> are the same.
>>
>
> What I meant is that there are a number of reasons to use linux-next
> as a base for your kernel (this being one of them) and few against.
>
> Arnd <><
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists