From: Fabio Rossi <rossi.f@inwind.it>
To: <seth.forshee@canonical.com>, Johannes Berg <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: Ensure off-channel frames don't get queued
Date: Mon, 25 Feb 2013 23:45:08 +0100 (CET) [thread overview]
Message-ID: <31632788.15939241361832308372.JavaMail.defaultUser@defaultHost> (raw)
On 25 Feb 2013 Seth wrote:
>Commit 6c17b77b67587b9f9e3070fb89fe98cef3187131 (mac80211: Fix tx queue
>handling during scans) contains a bug that causes off-channel frames to
>get queued when they should be handed down to the driver for transmit.
>Prevent this from happening.
>
>Reported-by: Fabio Rossi <rossi.f@inwind.it>
>Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
>---
>
>Fabio, this patch should fix the problem. Can you verify?
tested, now it works again
Fabio
next reply other threads:[~2013-02-25 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 22:45 Fabio Rossi [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-25 19:26 regression with kernel 3.8 Seth Forshee
2013-02-25 20:58 ` [PATCH] mac80211: Ensure off-channel frames don't get queued Seth Forshee
2013-02-26 20:16 ` 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=31632788.15939241361832308372.JavaMail.defaultUser@defaultHost \
--to=rossi.f@inwind.it \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=seth.forshee@canonical.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).