From: "John W. Linville" <linville@tuxdriver.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] mac80211: fix supported rates IE if AP doesn't give us it's rates
Date: Wed, 28 Apr 2010 16:33:04 -0400 [thread overview]
Message-ID: <20100428203304.GB2912@tuxdriver.com> (raw)
In-Reply-To: <20100428133336.GA2527@dhcp-lab-161.englab.brq.redhat.com>
On Wed, Apr 28, 2010 at 03:33:37PM +0200, Stanislaw Gruszka wrote:
> On Wed, Apr 28, 2010 at 03:17:04PM +0200, Stanislaw Gruszka wrote:
> > If AP do not provide us supported rates before assiociation, send
> > all rates we are supporting instead of empty information element.
>
> Please note these two patches together with "QoS fixes":
> - mac80211: explicitly disable/enable QoS
> - iwlwifi: manage QoS by mac stack
> resolve:
> https://bugzilla.redhat.com/show_bug.cgi?id=558002
>
> "QoS fixes" alone resolve:
> https://bugzilla.redhat.com/show_bug.cgi?id=539878
>
> So I think we want all 4 patches in stable.
>
> John,if possible push patches to Linus tree. When they lend there,
> I will post backported patches to stable ML. I have them already
> prepared ant tested for 2.6.32 :)
It is fairly late in the 2.6.34 cycle, and it isn't obvious to me
that these fix any sort of regression. Am I wrong?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-04-28 20:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 13:17 [PATCH 1/2] mac80211: do not wip out old supported rates Stanislaw Gruszka
2010-04-28 13:17 ` [PATCH 2/2] mac80211: fix supported rates IE if AP doesn't give us it's rates Stanislaw Gruszka
2010-04-28 13:33 ` Stanislaw Gruszka
2010-04-28 20:33 ` John W. Linville [this message]
2010-04-30 8:57 ` Stanislaw Gruszka
2010-04-28 13:39 ` Johannes Berg
2010-04-28 13:57 ` Stanislaw Gruszka
2010-04-28 13:59 ` Johannes Berg
2010-04-28 15:03 ` [PATCH 2/2 v2] " Stanislaw Gruszka
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=20100428203304.GB2912@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.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).