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-01-17
Date: Thu, 17 Jan 2013 14:50:56 -0500 (EST) [thread overview]
Message-ID: <20130117.145056.60689530330513006.davem@davemloft.net> (raw)
In-Reply-To: <20130117173239.GA2098@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Thu, 17 Jan 2013 12:32:40 -0500
> This batch of fixes is intended for 3.8...
>
> Included is a Bluetooth pull. Gustavo says:
>
> "A few fixes for 3.8. Five of them are just new devices ids addition.
> Apart from the that there is fix to a kernel memory leak to userspace from
> Anderson Lizardo, two interoperability fixes from Jaganath Kanakkassery and
> Szymon Janc. And a crash fix by me."
>
> Along with that, Amitkumar Karwar brings a pair of mwifiex fixes for
> problems related to handling of band information within the driver.
> These problems can lead to association failures.
>
> Sujith Manoharan fixes a memory leak in the ath9k_htc code (originally
> reported by Larry Finger).
>
> The big hero this round is Felix Fietkau. Felix gives us seven
> ath9k fixes, including a fix for a race condition, the removal of a
> double-free, and a fix for a deadlock, among others.
>
> These have all been in linux-next for at least a couple of days,
> with no complaints so far. Please let me know if there are problems!
Pulled, thanks John.
prev parent reply other threads:[~2013-01-17 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 17:32 John W. Linville
2013-01-17 19:50 ` 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=20130117.145056.60689530330513006.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®