linux-kernel - Re: Microblaze Linux release

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200804140538.30268.arnd@arndb.de>
Date:	Mon, 14 Apr 2008 05:38:28 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	monstr@...nam.cz
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

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 <><
--
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/