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]

Message-ID: <48061AA0.2000305@seznam.cz>
Date:	Wed, 16 Apr 2008 17:26:24 +0200
From:	Michal Simek <monstr@...nam.cz>
To:	Paul Mackerras <paulus@...ba.org>
Cc:	benh@...nel.crashing.org, Arnd Bergmann <arnd@...db.de>,
	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

Hi Paul,

> 
>> I think so. Sharing code among archs looks nice and this way is definitely
>> right. But starting with communication with PowerPC guys that this code I want
>> to use in case that this code is not in vanilla. This is not good start for
>> doing this.
> 
> I have a commit queued up that moves lmb.c into the top-level lib
> directory so other architectures can use it easily.  Dave Miller
> wanted this so he could use it for sparc64.  That will go into Linus'
> tree when the merge window opens and will be in 2.6.26.  So I don't
> see any reason why microblaze couldn't use the LMB stuff.
> 
> Paul.

I will test it.

Thanks Paul,

Michal Simek

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