Netdev List
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
To: linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Larry Finger
	<Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH 0/3 V2] iFixes for b43 and b43legacy
Date: Sun, 12 Jan 2014 15:11:36 -0600	[thread overview]
Message-ID: <1389561099-17181-1-git-send-email-Larry.Finger@lwfinger.net> (raw)

These 3 fixes should be applied as soon as possible. I understand that 3.13
will be released soon. As all 3 are marked for stable, inclusion in 3.14
will be satisfactory.

V2 - Patch 1 is unchanged, but 2 and 3 are fixed to remove any race conditions.

Larry


Larry Finger (3):
  b43: Fix lockdep splat
  b43: Fix unload oops if firmware is not available
  b43legacy: Fix unload oops if firmware is not available

 drivers/net/wireless/b43/b43.h        |  4 ++--
 drivers/net/wireless/b43/main.c       | 27 ++++++++++++++++-----------
 drivers/net/wireless/b43legacy/main.c |  1 +
 3 files changed, 19 insertions(+), 13 deletions(-)

-- 
1.8.4

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2014-01-12 21:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12 21:11 Larry Finger [this message]
2014-01-12 21:11 ` [PATCH 1/3 V2] b43: Fix lockdep splat Larry Finger
2014-01-12 21:11 ` [PATCH 2/3 V2] b43: Fix unload oops if firmware is not available Larry Finger
2014-01-12 21:11 ` [PATCH 3/3 V2] b43legacy: " 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=1389561099-17181-1-git-send-email-Larry.Finger@lwfinger.net \
    --to=larry.finger-tq5ms3gmjblk1umjsbkqmq@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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