From: "Arend van Spriel" <arend@broadcom.com>
To: "Greg KH" <gregkh@suse.de>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 3.1-stable] staging: brcm80211: fix for rate index in receive status
Date: Thu, 10 Nov 2011 19:50:32 +0100 [thread overview]
Message-ID: <4EBC1CF8.8080704@broadcom.com> (raw)
In-Reply-To: <20111110184457.GA8010@suse.de>
On 11/10/2011 07:44 PM, Greg KH wrote:
> On Thu, Nov 10, 2011 at 07:37:10PM +0100, Arend van Spriel wrote:
>> On 11/10/2011 04:17 PM, Greg KH wrote:
>>
>> Here it is:
>>
>> commit 5a84d6ad4c9306afb467a600a4c6d7b50da49440
>> Author: Arend van Spriel <arend@broadcom.com>
>> Date: Tue Aug 23 14:14:00 2011 +0200
>>
>> staging: brcm80211: fill in proper rx rate in mac80211 rx status
>>
>> The brcmsmac driver supports different rates on 5GHz but this is not
>> taken into account when providing the rate index in the receive
>> status information passed to mac80211.
>>
>> Reviewed-by: Roland Vossen <rvossen@broadcom.com>
>> Reviewed-by: Pieter-Paul Giesberts <pieterpg@broadcom.com>
>> Reviewed-by: Henry Ptasinski <henryp@broadcom.com>
>> Signed-off-by: Arend van Spriel <arend@broadcom.com>
>> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
>
> Thanks, that's what I need. I'll queue this up for the next 3.1 kernel
> after this one gets out later this week.
>
> greg k-h
>
Fine by me.
Gr. AvS
prev parent reply other threads:[~2011-11-10 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 9:48 [PATCH 3.1-stable] staging: brcm80211: fix for rate index in receive status Arend van Spriel
2011-11-10 15:17 ` Greg KH
2011-11-10 18:37 ` Arend van Spriel
2011-11-10 18:44 ` Greg KH
2011-11-10 18:50 ` Arend van Spriel [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=4EBC1CF8.8080704@broadcom.com \
--to=arend@broadcom.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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.