[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4803035D.5030400@seznam.cz>
Date: Mon, 14 Apr 2008 09:10:21 +0200
From: Michal Simek <monstr@...nam.cz>
To: Arnd Bergmann <arnd@...db.de>
CC: Stephen Neuendorffer <stephen.neuendorffer@...inx.com>,
John Williams <john.williams@...alogix.com>,
jwboyer@...ux.vnet.ibm.com, benh@...nel.crashing.org,
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,
paulus@...ba.org
Subject: Re: Microblaze Linux release
Hi Arnd,
>> I would like to ask you for review all microblaze code especially
>> arch/microblaze and include/asm-microblaze. Please don't send me question to
>> drivers - Microblaze will use only uartlite driver (only add on or to Kconfig -
>> that's enough for now).
>
> I'm certainly willing to help review it, but I think the timing is too short
> for asking for a 2.6.26 merge. Judging from experience, a new architecture
> review takes a few weeks to sort out all the issues you want resolved before
> merging, so posting them now would put you in a much more comfortable position
> when targeting a 2.6.27 merge.
Thanks for your help. I know that the time is short.:-( We'll see. I will
request for merge if I know Microblaze cpu is clean.
> One of the things I always wanted to have is a common location for all the
> things that get duplicated verbatim into each new architecture, like all
> the include/asm/{fcntl,ioctls,ipcbuf,mman,poll,posix_types,sem_buf}.h and
> others that define part of the syscall ABI.
>
> Arnd <><
Include files are pain I know.
Michal Simek
www.monstr.eu
--
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