mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless 2013-02-06
Date: Wed, 06 Feb 2013 14:53:20 -0500 (EST)	[thread overview]
Message-ID: <20130206.145320.721522259467415518.davem@davemloft.net> (raw)
In-Reply-To: <20130206193423.GI2148@tuxdriver.com>

From: "John W. Linville" <linville@tuxdriver.com>
Date: Wed, 6 Feb 2013 14:34:23 -0500

> Please consider this pull request for the 3.8 stream...
> 
> Included is a bluetooth pull.  Gustavo says:
> 
> "Two simple fixes for 3.8. One of the patches fixes a situation
> where the connection wasn't terminated if a timeout ocurrs for LE
> an SCO connections.  The other fixes prevent NULL dereference in the
> SMP code, it is a security fix as well."
> 
> Along with those...
> 
> Hauke Mehrtens provides a couple of ssb and bcma bus fixes that
> prevent oopses when unloading those modules.
> 
> Larry Finger provides and rtlwifi fix to avoid a "scheduling while
> atomic" bug.
> 
> Last but certainly not least, Arend van Spriel bring a brcmsmac fix that
> reworks the mac80211 .flush() callback in order to avoid the dreaded
> brcms_c_wait_for_tx_completion warnings.  This one looks a little
> large, but I think it is safe and isolated to brcmsmac in any case.
> 
> Please let me know if there are problems!

Pulled, even though the comments weren't styled correctly
in the bluetooth fixes.  Please fix that when this stuff
propagates into net-next, thanks.

      reply	other threads:[~2013-02-06 19:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 19:34 John W. Linville
2013-02-06 19:53 ` David Miller [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=20130206.145320.721522259467415518.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®