linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Stefano Brivio <stefano.brivio@polimi.it>,
	Michael Buesch <mb@bu3sch.de>,
	wireless <linux-wireless@vger.kernel.org>,
	Broadcom Linux <bcm43xx-dev@lists.berlios.de>
Subject: Re: [PATCH 2/2 V2] b43legacy: Fix locking problem
Date: Mon, 18 May 2009 16:03:54 -0400	[thread overview]
Message-ID: <20090518200354.GK2814@tuxdriver.com> (raw)
In-Reply-To: <4A0DD306.30705@lwfinger.net>

On Fri, May 15, 2009 at 03:39:34PM -0500, Larry Finger wrote:
> Commit abb1d2bca0fc429c136747a64e675dd4d8906f36 introduced a locking
> problem in b43legacy that caused the system to freeze upon booting.
> 
> Signed-off-by: Larry Finger@lwfinger.net
> ---
> 
> John,
> 
> This is 2.6.31 material. I hope that you do not have trouble with
> this patch. While on the road, my normal method is not available.
> 
> This is resent as V2 to eliminate some patch offsets that resulted
> from the changes in V2 of patch 1.
> 
> Larry

This conflicted w/ a patch from Johannes, and I couldn't easily
figure-out how to resolve them.  Since his claimed to fix something
else along with this problem, I just applied his.

Also, please don't refer to commit IDs directly, especially ones
that aren't already in linux-2.6.  Instead, please refer to the
patch subject.  If the commit is already in linux-2.6, then a short
reference to the commit ID is acceptable.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2009-05-18 20:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-15 20:39 [PATCH 2/2 V2] b43legacy: Fix locking problem Larry Finger
2009-05-18 20:03 ` John W. Linville [this message]
2009-05-19  3:33   ` Larry Finger
     [not found]     ` <200905191452419680632@temobi.com>
2009-05-19 14:32       ` Larry Finger

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=20090518200354.GK2814@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=stefano.brivio@polimi.it \
    /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).