From: Johannes Berg <johannes@sipsolutions.net>
To: Peter Oh <peter.oh@bowerswilkins.com>,
Arend van Spriel <arend.vanspriel@broadcom.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ieee80211: update public action codes
Date: Thu, 29 Jun 2017 09:57:42 +0200 [thread overview]
Message-ID: <1498723062.3141.0.camel@sipsolutions.net> (raw)
In-Reply-To: <ccd3208a-8235-ffbc-79cd-422115f5f3ab@bowerswilkins.com>
On Wed, 2017-06-28 at 13:24 -0700, Peter Oh wrote:
>
> On 06/28/2017 01:16 PM, Arend van Spriel wrote:
> > On 28-06-17 00:07, peter.oh@bowerswilkins.com wrote:
> > > From: Peter Oh <peter.oh@bowerswilkins.com>
> > >
> > > Update Public Action field values as updated in IEEE Std 802.11-
> > > 2016,
> > > so that modules/drivers can refer it.
> >
> > Hi Peter,
> >
> > I am pretty sure there are a lot of other definitions in the 802.11
> > spec
> > that are not in a linux header file. So are you planning on
> > submitting
> > driver patches using the added definitions. Stuff is mostly added
> > as needed.
I think that's mostly laziness though :-) I'm perfectly happy to have
all these values in even if we don't use them now - they're not going
to change by not using.
> I have extra patches that uses the new values, but doubt if it's fit
> to be upstream.
I guess you can try :)
johannes
next prev parent reply other threads:[~2017-06-29 7:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 22:07 [PATCH] ieee80211: update public action codes peter.oh
2017-06-28 20:16 ` Arend van Spriel
2017-06-28 20:24 ` Peter Oh
2017-06-29 7:57 ` Johannes Berg [this message]
2017-06-29 13:20 ` Johannes Berg
2017-06-30 5:52 ` Kalle Valo
2017-06-30 6:50 ` Kalle Valo
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=1498723062.3141.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=peter.oh@bowerswilkins.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).