From: Johannes Berg <johannes@sipsolutions.net>
To: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] cfg80211/nl80211: Enable drivers to implement mac address based ACL
Date: Wed, 12 Dec 2012 12:27:15 +0100 [thread overview]
Message-ID: <1355311635.9708.3.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1355311595.9708.2.camel@jlt4.sipsolutions.net> (sfid-20121212_122620_162346_E59A9D73)
On Wed, 2012-12-12 at 12:26 +0100, Johannes Berg wrote:
> Yeah but I don't think that's a valid general assumption, and with the
> feature advertising API that you came up with, the driver can't
> advertise that it supports both at the same time etc.
>
> Also, in fact, I think there needs to be more justification for why you
> need two lists to start with -- it seems to me that a white- and
> blacklist doesn't make sense at all, unless it's not really a white- and
> blacklist but one of
> 1) a blacklist
> 2) a whitelist + a "do not notify" list
And actually, without a notify mechanism (which I don't think exists
yet) this doesn't make sense anyway
johannes
next prev parent reply other threads:[~2012-12-12 11:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 11:46 [PATCH 1/2] cfg80211: Move the definition of struct mac_address up Vasanthakumar Thiagarajan
2012-12-07 11:46 ` [PATCH 2/2] cfg80211/nl80211: Enable drivers to implement mac address based ACL Vasanthakumar Thiagarajan
2012-12-11 19:57 ` Johannes Berg
2012-12-12 5:16 ` Vasanthakumar Thiagarajan
2012-12-12 11:26 ` Johannes Berg
2012-12-12 11:27 ` Johannes Berg [this message]
2012-12-13 4:56 ` Vasanthakumar Thiagarajan
2012-12-13 4:52 ` Vasanthakumar Thiagarajan
2012-12-13 5:47 ` Sujith Manoharan
2012-12-13 5:56 ` Vasanthakumar Thiagarajan
2012-12-12 10:14 ` Antonio Quartulli
2012-12-12 11:07 ` Vasanthakumar Thiagarajan
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=1355311635.9708.3.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=vthiagar@qca.qualcomm.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).