From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] cfg80211: keep track of supported interface modes
Date: Thu, 07 Aug 2008 15:55:37 -0400 [thread overview]
Message-ID: <1218138937.32083.23.camel@localhost.localdomain> (raw)
In-Reply-To: <1218138465.3630.60.camel@johannes.berg>
On Thu, 2008-08-07 at 21:47 +0200, Johannes Berg wrote:
> On Thu, 2008-08-07 at 14:13 -0400, Dan Williams wrote:
> > On Thu, 2008-08-07 at 17:21 +0200, Johannes Berg wrote:
> > > It is obviously good for userspace to know up front which interface modes
> > > a given piece of hardware might support (even if adding such an interface
> > > might fail later because of concurrency issues), so let's make cfg80211
> > > aware of that. For good measure, disallow adding interfaces in all other
> > > modes so drivers don't forget to announce support for one mode when they
> > > add it.
> >
> > This makes me happy.
>
> We discussed this in Ottawa, didn't we? It just slipped my mind and I
> remembered earlier today.
Yep, we did.
Dan
> No somebody just needs to go through and add the corresponding hunks for
> all drivers. *hint* :) (it mostly consists in seeing what the
> add_interface callback will accept, which is correct for all drivers but
> iwlwifi as far as I know)
>
> johannes
next prev parent reply other threads:[~2008-08-07 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 15:21 [RFC] cfg80211: keep track of supported interface modes Johannes Berg
2008-08-07 18:02 ` Luis R. Rodriguez
2008-08-07 19:45 ` Johannes Berg
2008-08-07 18:13 ` Dan Williams
2008-08-07 19:47 ` Johannes Berg
2008-08-07 19:55 ` Dan Williams [this message]
2008-08-15 20:16 ` Luis R. Rodriguez
2008-08-15 20:19 ` Luis R. Rodriguez
2008-08-15 23:16 ` Ivo van Doorn
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=1218138937.32083.23.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--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).