From: Johannes Berg <johannes@sipsolutions.net>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: arend@broadcom.com, linville@tuxdriver.com,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] brcm80211: rename CONFIG_BRCMUMAC to CONFIG_BRCMUTIL
Date: Thu, 13 Oct 2011 16:28:04 +0200 [thread overview]
Message-ID: <1318516084.5612.18.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1318515949-9558-1-git-send-email-hauke@hauke-m.de> (sfid-20111013_162620_528734_10EF53D2)
On Thu, 2011-10-13 at 16:25 +0200, Hauke Mehrtens wrote:
> There is no config option named CONFIG_BRCMUMAC this should be
> CONFIG_BRCMUTIL as this is missing here.
>
> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
> ---
> drivers/net/wireless/Makefile | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/wireless/Makefile b/drivers/net/wireless/Makefile
> index 0a304b0..812a050 100644
> --- a/drivers/net/wireless/Makefile
> +++ b/drivers/net/wireless/Makefile
> @@ -59,5 +59,5 @@ obj-$(CONFIG_IWM) += iwmc3200wifi/
>
> obj-$(CONFIG_MWIFIEX) += mwifiex/
> obj-$(CONFIG_BRCMFMAC) += brcm80211/
> -obj-$(CONFIG_BRCMUMAC) += brcm80211/
> +obj-$(CONFIG_BRCMUTIL) += brcm80211/
> obj-$(CONFIG_BRCMSMAC) += brcm80211/
Shouldn't it just go away since BRCMUTIL depends on SMAC||FMAC and is
otherwise unreachable?
johannes
next prev parent reply other threads:[~2011-10-13 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 14:25 [PATCH] brcm80211: rename CONFIG_BRCMUMAC to CONFIG_BRCMUTIL Hauke Mehrtens
2011-10-13 14:28 ` Johannes Berg [this message]
2011-10-13 15:12 ` Arend van Spriel
2011-11-09 20:27 ` [PATCH] wireless: cleanup brcm80211 bits in drivers/net/wireless/Makefile John W. Linville
2011-11-10 8:54 ` Arend van Spriel
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=1318516084.5612.18.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=hauke@hauke-m.de \
--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;
as well as URLs for NNTP newsgroup(s).