From: wwguy <wey-yi.w.guy@intel.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dave Airlie <airlied@gmail.com>,
Stanislaw Gruszka <sgruszka@redhat.com>
Subject: Re: [PATCH] iwlegacy: make iwl3945 and iwl4965 select IWLWIFI_LEGACY
Date: Mon, 11 Apr 2011 11:39:22 -0700 [thread overview]
Message-ID: <1302547162.5663.2.camel@wwguy-ubuntu> (raw)
In-Reply-To: <1302541599-15383-1-git-send-email-linville@tuxdriver.com>
On Mon, 2011-04-11 at 10:06 -0700, John W. Linville wrote:
> Otherwise, IWLWIFI_LEGACY has to be selected independently before the
> drivers are made available.
>
> Reported-by: Dave Airlie <airlied@gmail.com>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
> Cc: Stanislaw Gruszka <sgruszka@redhat.com>
> Cc: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> ---
> drivers/net/wireless/iwlegacy/Kconfig | 9 +++++----
> 1 files changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/wireless/iwlegacy/Kconfig b/drivers/net/wireless/iwlegacy/Kconfig
> index 2a45dd4..aef65cd 100644
> --- a/drivers/net/wireless/iwlegacy/Kconfig
> +++ b/drivers/net/wireless/iwlegacy/Kconfig
> @@ -1,6 +1,5 @@
> config IWLWIFI_LEGACY
> - tristate "Intel Wireless Wifi legacy devices"
> - depends on PCI && MAC80211
> + tristate
> select FW_LOADER
> select NEW_LEDS
> select LEDS_CLASS
Should we add some ---help--- here?, or not..
Wey
next prev parent reply other threads:[~2011-04-11 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTimoDVMcvFdoUedyfw4Thv8=DsV-5A@mail.gmail.com>
2011-04-11 17:06 ` [PATCH] iwlegacy: make iwl3945 and iwl4965 select IWLWIFI_LEGACY John W. Linville
2011-04-11 18:39 ` wwguy [this message]
2011-04-11 18:58 ` 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=1302547162.5663.2.camel@wwguy-ubuntu \
--to=wey-yi.w.guy@intel.com \
--cc=airlied@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sgruszka@redhat.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).