From: Ingo Molnar <mingo@elte.hu>
To: "H. Peter Anvin" <hpa@kernel.org>
Cc: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>,
x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
ath9k-devel@venema.h4ckr.net, linux-wireless@vger.kernel.org
Subject: Re: tip - Solution of ath9k: turn off temporarily (66b5c4a2c638b5a69d3e41abe4a2bae55035a92e)
Date: Fri, 2 Jan 2009 20:58:02 +0100 [thread overview]
Message-ID: <20090102195802.GA28494@elte.hu> (raw)
In-Reply-To: <495E6C96.3040102@kernel.org>
* H. Peter Anvin <hpa@kernel.org> wrote:
> Jaswinder Singh Rajput wrote:
> >>
> >> diff --git a/drivers/net/wireless/ath9k/Kconfig b/drivers/net/wireless/ath9k/Kconfig
> >> index c43bd32..b849a45 100644
> >> --- a/drivers/net/wireless/ath9k/Kconfig
> >> +++ b/drivers/net/wireless/ath9k/Kconfig
> >> @@ -1,6 +1,8 @@
> >> config ATH9K
> >> tristate "Atheros 802.11n wireless cards support"
> >> depends on PCI && MAC80211 && WLAN_80211
> >> + # build failures
> >> + depends on 0
> >> select MAC80211_LEDS
> >> select LEDS_CLASS
> >> select NEW_LEDS
> >>
> >
>
> I thought the proper way to do this was "depends on BROKEN"...
this was just a temporary hack to work around a mild regression in -git
that i'm sure will be sorted out in short order (if it has not been
already).
CONFIG_BROKEN is a much different category: it blacklists ridiculously
stale or mortally broken features/drivers, as a last warning before they
get removed for good. I dont use it in such temporary, not-for-upstream
testing hacks (even though the end result is obviously the same as
'depends on 0') - i didnt even have time to properly report the build
breakage.
Ingo
next prev parent reply other threads:[~2009-01-02 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3f9a31f40901020936l4bed87e2jb64678572d2ad45b@mail.gmail.com>
[not found] ` <20090102180730.GA10072@elte.hu>
2009-01-02 18:40 ` tip - Solution of ath9k: turn off temporarily (66b5c4a2c638b5a69d3e41abe4a2bae55035a92e) Jaswinder Singh Rajput
2009-01-02 19:35 ` H. Peter Anvin
2009-01-02 19:58 ` Ingo Molnar [this message]
2009-01-05 11:51 ` [PATCH] ath9k: Enforce module build if rfkill is a module Jouni Malinen
2009-01-05 14:04 ` Ingo Molnar
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=20090102195802.GA28494@elte.hu \
--to=mingo@elte.hu \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=hpa@kernel.org \
--cc=jaswinderlinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=x86@kernel.org \
/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).