linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@kernel.org
Subject: Re: [PATCH 3.1-stable] staging: brcm80211: fix for rate index in receive status
Date: Thu, 10 Nov 2011 07:17:46 -0800	[thread overview]
Message-ID: <20111110151746.GB29104@suse.de> (raw)
In-Reply-To: <1320918514-5916-1-git-send-email-arend@broadcom.com>

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@schottelius.org>

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

> Cc: stable@kernel.org

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

> Reported-by: Nico Schottelius <nico-linux-20111017@schottelius.org>
> Signed-off-by: Arend van Spriel <arend@broadcom.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

  reply	other threads:[~2011-11-10 15:18 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 [this message]
2011-11-10 18:37   ` Arend van Spriel
2011-11-10 18:44     ` Greg KH
2011-11-10 18:50       ` Arend van Spriel

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=20111110151746.GB29104@suse.de \
    --to=gregkh@suse.de \
    --cc=arend@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=stable@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 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).