From: Johannes Berg <johannes@sipsolutions.net>
To: Eliad Peller <eliad@wizery.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
John Linville <linville@tuxdriver.com>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Wireless problem in 3.4-rc5
Date: Tue, 08 May 2012 12:57:21 +0200 [thread overview]
Message-ID: <1336474641.4320.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAB3XZEd7H683Gc_2Ytw7-LByOOGy5o_hRsuE3cjLhrONFc=6tg@mail.gmail.com> (sfid-20120508_110047_096982_8A84E6AC)
On Tue, 2012-05-08 at 12:00 +0300, Eliad Peller wrote:
> On Tue, May 8, 2012 at 11:32 AM, Eliad Peller <eliad@wizery.com> wrote:
> > On Mon, May 7, 2012 at 2:30 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
> >>> > i'm not sure this is related to the problem you're facing, but the
> >>> > commit above seems to have some bug in which a packet might get
> >>> > enqueued on invalid queue (0xff) - please try this patch (compile
> >>> > tested only):
> >>
> >> Eliad, can you submit that patch with more details?
> >>
> > sure, i'll send it soon.
> >
> i've just figured it that it doesn't seem to have any effect, as the
> hw_queue will get overridden anyway in ieee80211_tx (because
> IEEE80211_HW_QUEUE_CONTROL is not set), so i'm not sure it's really
> needed. do you want me to send it anyway?
Still seems cleaner to me, I think
johannes
prev parent reply other threads:[~2012-05-08 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 19:58 Wireless problem in 3.4-rc5 Larry Finger
2012-05-02 12:58 ` Eliad Peller
2012-05-02 20:17 ` Larry Finger
2012-05-07 11:30 ` Johannes Berg
2012-05-08 8:32 ` Eliad Peller
2012-05-08 9:00 ` Eliad Peller
2012-05-08 10:57 ` Johannes Berg [this message]
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=1336474641.4320.0.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=eliad@wizery.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).