From: "John W. Linville" <linville@tuxdriver.com>
To: davem@davemloft.net
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless 2012-01-04 #2
Date: Wed, 4 Jan 2012 11:57:52 -0500 [thread overview]
Message-ID: <20120104165752.GH2540@tuxdriver.com> (raw)
In-Reply-To: <20120104164339.GG2540@tuxdriver.com>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
On Wed, Jan 04, 2012 at 11:43:40AM -0500, John W. Linville wrote:
> Dave,
>
> Here are a handful of straggler wireless fixes for 3.2. Included is
> a NULL pointer fix for mwifiex, a regression fix for handling rx
> header lengths for differnt b43 firmwares in PIO mode, a revert of
> a one-liner for Bluetooth HCI that was causing uncomfortable delays
> during resume, and an ath9k fix for a panic when running in AP mode
> with aggregation disabled.
>
> The Bluetooth fix is a one-liner change of a delay value. The mwifiex,
> b43, and ath9k fixes are relatively small and isolated to their
> respective drivers.
>
> Please let me know if there are problems!
>
> John
>
> ---
>
> The following changes since commit 405cc2736527bd506fd8f652308b03b2c8a1e8b9:
>
> fix CAN MAINTAINERS SCM tree type (2012-01-03 14:57:43 -0500)
>
> are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless.git for-davem
The top of the tree here is commit d8f46ff11081f03b09efe82245a3257bab6bf60e.
Thanks,
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-04 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 16:43 pull request: wireless 2012-01-04 #2 John W. Linville
2012-01-04 16:57 ` John W. Linville [this message]
2012-01-04 19:49 ` David Miller
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=20120104165752.GH2540@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.