linux-kernel - Re: [PATCH 3.1-stable] staging: brcm80211: fix for rate index in receive status

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111110151746.GB29104@suse.de>
Date:	Thu, 10 Nov 2011 07:17:46 -0800
From:	Greg KH <gregkh@...e.de>
To:	Arend van Spriel <arend@...adcom.com>
Cc:	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org,
	stable@...nel.org
Subject: Re: [PATCH 3.1-stable] staging: brcm80211: fix for rate index in
 receive status

On Thu, Nov 10, 2011 at 10:48:34AM +0100, Arend van Spriel wrote:
> This fix resolves an issue on 5GHz as posted on LKML:
> 
> BUG: All network processes hang (brcmsmac/wpa_supplicant)
> ID: <20111018111422.GA1979@...ottelius.org>

What are these tags for?  I've not seen them in kernel patches before.

> Cc: stable@...nel.org

Wrong address, please use stable@...r.kernel.org now.

> Reported-by: Nico Schottelius <nico-linux-20111017@...ottelius.org>
> Signed-off-by: Arend van Spriel <arend@...adcom.com>
> ---
> Hi Greg,
> 
> This change is in the mainline brcmsmac driver, but I do not have a commit
> message to refer to as we transitioned from staging to mainline in the last
> merge window. Can you process this patch without that info?

No, I need the git commit id of the patch that fixed this in Linus's
tree, if the files are different due to the move, that's fine, but I
still need this to reference.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/