From: Johannes Berg <johannes@sipsolutions.net>
To: Jaswinder Singh Rajput <jaswindernetwork@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: CFG80211 depends on RFKILL or not
Date: Tue, 09 Feb 2010 16:09:12 +0100 [thread overview]
Message-ID: <1265728152.3783.37.camel@johannes.berg> (raw)
In-Reply-To: <74ccb2ee1002090631i4a29d320u2756af13de05cb97@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
On Tue, 2010-02-09 at 20:01 +0530, Jaswinder Singh Rajput wrote:
> I am trying to understand what is the magic behind :
>
> 19 config CFG80211
> 20 tristate "cfg80211 - wireless configuration API"
> 21 depends on RFKILL || !RFKILL
>
> Do we really need RFKILL and !RFKILL
Yes. You can not have RFKILL, or you can have CFG80211 depend on RFKILL,
but you can NOT have CFG80211=y and RFKILL=m.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2010-02-09 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 14:31 CFG80211 depends on RFKILL or not Jaswinder Singh Rajput
2010-02-09 15:09 ` Johannes Berg [this message]
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=1265728152.3783.37.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=jaswindernetwork@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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