From: Michal Marek <mmarek@suse.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC v5 4/5] mac80211: use Kconfig counters to elide unnecessary code
Date: Fri, 20 Nov 2015 17:37:54 +0100 [thread overview]
Message-ID: <564F4C62.2070006@suse.com> (raw)
In-Reply-To: <1448033373.3141.46.camel@sipsolutions.net>
On 2015-11-20 16:29, Johannes Berg wrote:
> On Fri, 2015-11-20 at 16:24 +0100, Michal Marek wrote:
>> On 2015-11-12 23:00, Johannes Berg wrote:
>>> + count MAC80211_NUM_DRIVERS
>>> + select MAC80211_DRIVER_NO_HWFLAGS
>>
>> Hi Johannes,
>>
>> The MAC80211_DRIVER_NO_HWFLAGS config does not seem to be used
>> anywhere in the logic.
>>
>
> Yeah, I forgot in this version. I have an updated one at
>
> https://git.kernel.org/cgit/linux/kernel/git/jberg/mac80211-next.git/lo
> g/?h=hwflags-elide
OK.
> haven't sent it yet though because I'm not really sure it's worth it at
> all?
I did not have time to look at your series until today.
Michal
next prev parent reply other threads:[~2015-11-20 16:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 22:00 [RFC v5 0/5] mac80211: elide code for static hw flags Johannes Berg
2015-11-12 22:00 ` [RFC v5 1/5] kconfig: introduce "count" Johannes Berg
2015-11-12 22:00 ` [RFC v5 2/5] kconfig: regenerate the shipped files Johannes Berg
2015-11-12 22:00 ` [RFC v5 3/5] mac80211: generate hw flags from include file Johannes Berg
2015-11-12 22:00 ` [RFC v5 4/5] mac80211: use Kconfig counters to elide unnecessary code Johannes Berg
2015-11-13 9:48 ` Julian Calaby
2015-11-13 9:52 ` Johannes Berg
2015-11-13 9:55 ` Johannes Berg
2015-11-20 15:24 ` Michal Marek
2015-11-20 15:29 ` Johannes Berg
2015-11-20 16:37 ` Michal Marek [this message]
2015-11-23 14:52 ` Michal Marek
2015-11-23 14:58 ` Johannes Berg
2015-11-23 15:06 ` Michal Marek
2015-11-23 15:15 ` Johannes Berg
2015-11-12 22:00 ` [RFC v5 5/5] iwlwifi: mvm: add Kconfig settings for hw flags Johannes Berg
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=564F4C62.2070006@suse.com \
--to=mmarek@suse.com \
--cc=johannes@sipsolutions.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).