From: Andrew Morton <akpm@linux-foundation.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
Marcel Holtmann <marcel@holtmann.org>,
"John W. Linville" <linville@tuxdriver.com>,
Michael Buesch <mb@bu3sch.de>, Richard Purdie <rpurdie@rpsys.net>,
netdev@vger.kernel.org
Subject: Re: s390 allmodconfig
Date: Fri, 2 Mar 2007 03:20:05 -0800 [thread overview]
Message-ID: <20070302032005.93a36b81.akpm@linux-foundation.org> (raw)
In-Reply-To: <1172833908.3482.20.camel@johannes.berg>
On Fri, 02 Mar 2007 12:11:48 +0100 Johannes Berg <johannes@sipsolutions.net> wrote:
> 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.
>
OK, thanks.
fwiw, http://userweb.kernel.org/~akpm/cross-compilers/ has an s390
cross-compiler binary.
next prev parent reply other threads:[~2007-03-02 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 8:18 s390 allmodconfig Andrew Morton
2007-03-02 8:25 ` Andrew Morton
2007-03-02 10:32 ` Richard Purdie
2007-03-02 11:01 ` Andrew Morton
2007-03-02 10:38 ` Johannes Berg
2007-03-02 11:06 ` Andrew Morton
2007-03-02 11:11 ` Johannes Berg
2007-03-02 11:20 ` Andrew Morton [this message]
2007-03-02 17:48 ` Martin Schwidefsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070302032005.93a36b81.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=johannes@sipsolutions.net \
--cc=linville@tuxdriver.com \
--cc=marcel@holtmann.org \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=schwidefsky@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).