From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"mcgrof@infradead.org" <mcgrof@infradead.org>, <it@atheros.com>
Subject: Re: [PATCH] compat-wireless: build led support conditionally
Date: Wed, 22 Dec 2010 13:57:18 -0500 [thread overview]
Message-ID: <20101222185718.GE8384@tux> (raw)
In-Reply-To: <4D1247C2.6090500@hauke-m.de>
On Wed, Dec 22, 2010 at 10:47:30AM -0800, Hauke Mehrtens wrote:
> On 12/22/2010 07:23 PM, Luis R. Rodriguez wrote:
> > On Wed, Dec 22, 2010 at 1:10 PM, Hauke Mehrtens <hauke@hauke-m.de> wrote:
> >> diff --git a/config.mk b/config.mk
> >> index 964c646..1f95908 100644
> >> --- a/config.mk
> >> +++ b/config.mk
> >> @@ -133,7 +133,9 @@ CONFIG_COMPAT_MAC80211_RC_DEFAULT=minstrel_ht
> >> CONFIG_MAC80211_RC_PID=y
> >> CONFIG_MAC80211_RC_MINSTREL=y
> >> CONFIG_MAC80211_RC_MINSTREL_HT=y
> >> +ifdef CONFIG_LEDS_TRIGGERS
> >> CONFIG_MAC80211_LEDS=y
> >> +endif #CONFIG_LEDS_TRIGGERS
> >
> > Without using a space for the ifdef'd variable the
> > include/linux/compat_autoconf.h will end up still defining it but you
> > should not get it set on the local Makefiles, in this case we want it
> > to not be defined in the compat_autoconf.h as well so how about
> > instead (handing off to my atheros address as I use mutt there, one
> > second)
>
> The script generating include/linux/compat_autoconf.h will also add the
> ifdefs into compat_autoconf.h. The generated entry looks like this:
>
> #if defined(CONFIG_LEDS_TRIGGERS) || defined(CONFIG_LEDS_TRIGGERS_MODULE)
> #ifndef CONFIG_MAC80211_LEDS
> #define CONFIG_MAC80211_LEDS 1
> #endif /* CONFIG_MAC80211_LEDS */
> #endif /* CONFIG_LEDS_TRIGGERS */
>
> I added this feature some months ago.
Ah neat thanks!
> Hauke
>
> Your mail server at atheros did not accept my mail, because the IP
> address I got from my local ISP ( 91.97.249.71 ) is on some blacklist.
> But this is normal and the mail was sent throught my mail server which
> IP address is not on that blacklist. Your mail server seams to be mis
> configured.
Cc'ing our IT.
Luis
next prev parent reply other threads:[~2010-12-22 18:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 18:10 [PATCH] compat-wireless: build led support conditionally Hauke Mehrtens
2010-12-22 18:23 ` Luis R. Rodriguez
2010-12-22 18:31 ` Luis R. Rodriguez
2010-12-22 18:47 ` Hauke Mehrtens
2010-12-22 18:57 ` Luis R. Rodriguez [this message]
2010-12-22 22:57 ` Luis R. Rodriguez
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=20101222185718.GE8384@tux \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=hauke@hauke-m.de \
--cc=it@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@infradead.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).