From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756210AbYDNDkG (ORCPT ); Sun, 13 Apr 2008 23:40:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753522AbYDNDjz (ORCPT ); Sun, 13 Apr 2008 23:39:55 -0400 Received: from moutng.kundenserver.de ([212.227.126.188]:49483 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751999AbYDNDjy (ORCPT ); Sun, 13 Apr 2008 23:39:54 -0400 From: Arnd Bergmann To: monstr@seznam.cz Subject: Re: Microblaze Linux release Date: Mon, 14 Apr 2008 05:38:28 +0200 User-Agent: KMail/1.9.9 Cc: Stephen Neuendorffer , John Williams , jwboyer@linux.vnet.ibm.com, benh@kernel.crashing.org, John Linn , git-dev@xilinx.com, Grant Likely , git@xilinx.com, microblaze-uclinux@itee.uq.edu.au, linux-kernel@vger.kernel.org, paulus@samba.org References: <48020A21.4000404@seznam.cz> In-Reply-To: <48020A21.4000404@seznam.cz> X-Face: I@=L^?./?$U,EK.)V[4*>`zSqm0>65YtkOe>TFD'!aw?7OVv#~5xd\s,[~w]-J!)|%=]>=?utf-8?q?+=0A=09=7EohchhkRGW=3F=7C6=5FqTmkd=5Ft=3FLZC=23Q-=60=2E=60Y=2Ea=5E?= =?utf-8?q?3zb?=) =?utf-8?q?+U-JVN=5DWT=25cw=23=5BYo0=267C=26bL12wWGlZi=0A=09=7EJ=3B=5Cwg?= =?utf-8?q?=3B3zRnz?=,J"CT_)=\H'1/{?SR7GDu?WIopm.HaBG=QYj"NZD_[zrM\Gip^U MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200804140538.30268.arnd@arndb.de> X-Provags-ID: V01U2FsdGVkX18SvTtfxF/WRKjE8ymfcDQr/To6WknQ0NQbBrH MsBWls1gxcyY0WelXckzL8EnVKJqRWuVNWvYuCOemAcfCjY4xL VvcBIkxlsNzoHYlIvgtJA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sunday 13 April 2008, Michal Simek wrote: > 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. 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 <><