Re: Microblaze Linux release

[Michal Simek]

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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/