From: Andrew Morton <akpm@linux-foundation.org>
To: Johannes Berg <johannes@sipsolutions.net>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: 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:06:46 -0800 [thread overview]
Message-ID: <20070302030646.0930d263.akpm@linux-foundation.org> (raw)
In-Reply-To: <1172831904.3482.13.camel@johannes.berg>
On Fri, 02 Mar 2007 11:38:24 +0100 Johannes Berg <johannes@sipsolutions.net> wrote:
> On Fri, 2007-03-02 at 00:25 -0800, Andrew Morton wrote:
>
> > Probably related to the Kconfig problems.
>
> Yeah, it is. s390 is funny, it doesn't include drivers/Kconfig, I don't
> think anybody of us would have suspected that.
>
> There doesn't seem to be a reason why it shouldn't have drivers/leds
> though. drivers/ssb I don't know about, does s390 have pci or pcmcia?
No, s390 doesn't have PCI.
> And the bluetooth stuff is also plain weird, I suppose s390 really
> should include drivers/hid/Kconfig :)
>
> Same with drivers/char that includes hw_random.
>
> Is there any reason it isn't including drivers/Kconfig?
>
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.
> I can offer below patch to fix the LED trigger problem, it's probably
> cleaner to depend on LEDS_TRIGGERS rather than selecting it and
> NEW_LEDS.
>
> johannes
>
> --- wireless-dev.orig/net/mac80211/Kconfig 2007-03-02 11:18:45.464333268 +0100
> +++ wireless-dev/net/mac80211/Kconfig 2007-03-02 11:33:24.534333268 +0100
> @@ -13,9 +13,7 @@ config MAC80211
>
> config MAC80211_LEDS
> bool "Enable LED triggers"
> - depends on MAC80211
> - select NEW_LEDS
> - select LEDS_TRIGGERS
> + depends on MAC80211 && LEDS_TRIGGERS
> ---help---
> This option enables a few LED triggers for different
> packet receive/transmit events.
OK, I'll try that, thanks.
next prev parent reply other threads:[~2007-03-02 11:09 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 [this message]
2007-03-02 11:11 ` Johannes Berg
2007-03-02 11:20 ` Andrew Morton
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=20070302030646.0930d263.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).