All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Nikolai ZHUBR <zhubr@mail.ru>, linux-wireless@vger.kernel.org
Subject: Re: ieee80211_tx_status: headroom too small
Date: Sat, 31 Oct 2009 11:23:35 +0100	[thread overview]
Message-ID: <1256984615.3555.122.camel@johannes.local> (raw)
In-Reply-To: <200910311117.22300.IvDoorn@gmail.com>

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

On Sat, 2009-10-31 at 11:17 +0100, Ivo van Doorn wrote:

> At the least the beacons, but I am not sure about if there are other frame types
> which also have this requirement.

So you align them all right now? Just wondering since beacons shouldn't
be status-reported.

johannes

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

  reply	other threads:[~2009-10-31 10:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-30 20:00 ieee80211_tx_status: headroom too small Nikolai ZHUBR
2009-10-30 20:03 ` Luis R. Rodriguez
2009-10-30 20:49   ` Re[2]: " Nikolai ZHUBR
2009-10-30 20:59 ` Johannes Berg
2009-10-30 21:56   ` Re[2]: " Nikolai ZHUBR
2009-10-31  5:46     ` Johannes Berg
2009-10-31  8:51       ` Ivo van Doorn
2009-10-31  8:56         ` Johannes Berg
2009-10-31  8:59           ` Ivo van Doorn
2009-10-31  9:25             ` Johannes Berg
2009-10-31  9:30               ` Ivo van Doorn
2009-10-31  9:34                 ` Johannes Berg
2009-10-31  9:44                   ` Ivo van Doorn
2009-10-31 10:03                     ` Johannes Berg
2009-10-31 10:17                       ` Ivo van Doorn
2009-10-31 10:23                         ` Johannes Berg [this message]
2009-10-31 10:33                           ` Ivo van Doorn
2009-10-31 14:24                   ` Re[2]: " Nikolai ZHUBR
2009-10-31 15:35                     ` Johannes Berg
2009-10-31 17:42                       ` Re[4]: " Nikolai ZHUBR
2009-11-21  1:30 David Ellingsworth

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=1256984615.3555.122.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zhubr@mail.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.