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
| ||
|
Date: Fri, 02 Mar 2007 12:11:48 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Martin Schwidefsky <schwidefsky@...ibm.com>,
Marcel Holtmann <marcel@...tmann.org>,
"John W. Linville" <linville@...driver.com>,
Michael Buesch <mb@...sch.de>,
Richard Purdie <rpurdie@...ys.net>, netdev@...r.kernel.org
Subject: Re: s390 allmodconfig
On Fri, 2007-03-02 at 03:06 -0800, Andrew Morton wrote:
> No, s390 doesn't have PCI.
Ok.
> s390 is weird ;) There's no way it'll support any of the hardware which you're
> working on (until they release the s390 laptop). So all we really want to
> do here is to avoid breaking s390 allmodconfig.
Alright. I think we'll probably have to make bcm43xx and b44 depend on
SSB instead of selecting it like the LED trigger stuff below.
But I don't see why s390 can't include hw random, led trigger or even
hid, those are all software features afaict.
> OK, I'll try that, thanks.
Not that it'll actually help get the compile through... bcm43xx will
drop fail and bluetooth probably as well.
johannes
Download attachment "signature.asc" of type "application/pgp-signature" (191 bytes)
Powered by blists - more mailing lists