From: Johannes Berg <johannes@sipsolutions.net>
To: Clyde McPherson <ccmcphe@verizon.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Wireless and RFKILL, this way integrators like myself
Date: Tue, 09 Nov 2010 10:53:07 -0800 [thread overview]
Message-ID: <1289328787.3660.3.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4CD99096.5020105@verizon.net>
On Tue, 2010-11-09 at 13:19 -0500, Clyde McPherson wrote:
> I build and use the compat-wireless source for use with SBC
> applications, and I have a question about the wireless portion of the
> code. Our SBCs do not have RFKILL capabilities, and since we use
> wireless we are forced to include it in our kernel due to the depends in
> wireless.
Not true. The depends is "depends on RFKILL || !RFKILL".
> What are the chances of adding #ifdef's for CONFIG_RFKILL on
> the code segments that require RFKILL
Zero, because if you configure w/o RFKILL then the rfkill functions all
become stubs and there's nothing for you to worry about.
johannes
next prev parent reply other threads:[~2010-11-09 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 18:19 Wireless and RFKILL Clyde McPherson
2010-11-09 18:53 ` Johannes Berg [this message]
2010-11-09 18:57 ` John W. Linville
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=1289328787.3660.3.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ccmcphe@verizon.net \
--cc=linux-wireless@vger.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).