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 2/3] mac80211: Make use of the new F_TX_NOACK and F_TX_NOSEQ Radiotap TX flags
Date: Sat, 13 Dec 2008 00:01:52 +0100 [thread overview]
Message-ID: <1229122912.3565.26.camel@johannes.berg> (raw)
In-Reply-To: <69e28c910812121500n67e45a52lb589833d84413adf@mail.gmail.com> (sfid-20081213_000004_022743_889F33D2)
[-- Attachment #1: Type: text/plain, Size: 823 bytes --]
On Sat, 2008-12-13 at 00:00 +0100, Stefanik Gábor wrote:
> On Fri, Dec 12, 2008 at 11:52 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > On Fri, 2008-12-12 at 23:51 +0100, Stefanik Gábor wrote:
> >
> >> But if we redefine !ASSIGN_SEQ to mean "use the sequence number
> >> supplied by userspace", we will need a new flag to distinguish between
> >> driver-level vs. stack-level sequence number assignments, which is
> >> essentially the same as this patch. There is no way to switch between
> >> 3 states (control in driver, stack or userspace) using only one bit.
> >
> > Good point, I forgot about that. But that isn't true for no-ack :)
> >
> > johannes
> >
>
> By the way, here is a bit more about the oops:
For that to make any sense, you'd have to show me the code too :)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-12-12 23:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 22:32 [RFC 2/3] mac80211: Make use of the new F_TX_NOACK and F_TX_NOSEQ Radiotap TX flags Stefanik Gábor
2008-12-12 22:39 ` Johannes Berg
2008-12-12 22:43 ` Stefanik Gábor
2008-12-12 22:45 ` Johannes Berg
2008-12-12 22:51 ` Stefanik Gábor
2008-12-12 22:52 ` Johannes Berg
2008-12-12 23:00 ` Stefanik Gábor
2008-12-12 23:01 ` Johannes Berg [this message]
2008-12-12 22:56 ` 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=1229122912.3565.26.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