From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: David Young <dyoung-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
Cc: radiotap <radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org>
Subject: Re: [RFA] RX flags
Date: Fri, 13 Mar 2009 12:41:01 +0100 [thread overview]
Message-ID: <1236944461.5235.28.camel@johannes.local> (raw)
In-Reply-To: <20090219020416.GM17342-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
On Wed, 2009-02-18 at 20:04 -0600, David Young wrote:
> Thanks for bringing the proposal, Johannes. I will update NetBSD to
> agree with these field definitions, if their are not objections in the
> timeline you have described:
>
> > Barring objections, I will repost the normative changes on in two weeks
> > time (Feb 23.) to be adopted on March 2, at which point I will make the
> > changes to the radiotap.org website and post the Linux patch for
> > inclusion.
Sorry, I was away for a couple of weeks on business and vacation, I'll
repost the changes now and make the wiki change.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-03-13 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 18:00 [RFA] RX flags Johannes Berg
[not found] ` <1234172982.4175.184.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-02-19 2:04 ` David Young
[not found] ` <20090219020416.GM17342-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
2009-03-13 11:41 ` Johannes Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-26 11:14 Johannes Berg
[not found] ` <1214478891.20763.38.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-07-07 18:12 ` David Young
[not found] ` <20080707181217.GL1269-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
2008-07-08 9:51 ` 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=1236944461.5235.28.camel@johannes.local \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=dyoung-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org \
--cc=radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.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).