Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Stefanik Gábor" <netrolller.3d@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 0/3] cfg80211, mac80211: Introduce radiotap flags for finer userspace control of injection
Date: Fri, 12 Dec 2008 23:57:43 +0100	[thread overview]
Message-ID: <1229122663.3565.24.camel@johannes.berg> (raw)
In-Reply-To: <69e28c910812121454t7d765b27l918e2f6162bd3f08@mail.gmail.com> (sfid-20081212_235405_000913_4548C728)

[-- Attachment #1: Type: text/plain, Size: 467 bytes --]

On Fri, 2008-12-12 at 23:54 +0100, Stefanik Gábor wrote:

> Using an "assign seqno" flag would cause existing injectors that
> expect the kernel to do seq numbering for them to fail. This possibly
> includes hostap and penumbra.

Yeah, I know, but can hostapd/penumbra really expect getting seqnos on
other platforms? If not, then for the sake of interoperability it might
make sense to switch around and have hostapd/penumbra just set the bit.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2008-12-12 22:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12 22:32 [RFC 0/3] cfg80211, mac80211: Introduce radiotap flags for finer userspace control of injection Stefanik Gábor
2008-12-12 22:37 ` Johannes Berg
2008-12-12 22:40   ` Stefanik Gábor
2008-12-12 22:42     ` Johannes Berg
2008-12-12 22:50     ` Johannes Berg
2008-12-12 22:54       ` Stefanik Gábor
2008-12-12 22:57         ` Johannes Berg [this message]
2008-12-13  0:20   ` Richard Farina
2008-12-13  0:26     ` 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=1229122663.3565.24.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netrolller.3d@gmail.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