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 2012-08-10
Date: Fri, 10 Aug 2012 16:27:19 -0700 (PDT) [thread overview]
Message-ID: <20120810.162719.2120897808611880641.davem@davemloft.net> (raw)
In-Reply-To: <20120810183351.GD1950@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Fri, 10 Aug 2012 14:33:51 -0400
> Here is a handful of fixes intended for 3.6.
>
> Daniel Drake offers a cfg80211 fix to consume pending events before
> taking a wireless device down. This prevents a resource leak.
>
> Stanislaw Gruszka gives us a fix for a NULL pointer dereference in
> rt61pci.
>
> Johannes Berg provides an iwlwifi patch to disable "greenfield" mode.
> Use of that mode was causing a rate scaling problem in for iwlwifi.
>
> Please let me know if there are problems!
Pulled, thanks John.
prev parent reply other threads:[~2012-08-10 23:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 18:33 pull request: wireless 2012-08-10 John W. Linville
2012-08-10 23:27 ` 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=20120810.162719.2120897808611880641.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;
as well as URLs for NNTP newsgroup(s).