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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Wed, 16 Apr 2008 17:33:03 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	monstr@...nam.cz
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

On Wednesday 16 April 2008, Michal Simek wrote:
> > 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/