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-01-27
Date: Fri, 27 Jan 2012 20:42:10 -0500 (EST) [thread overview]
Message-ID: <20120127.204210.1693783796267469687.davem@davemloft.net> (raw)
In-Reply-To: <20120127201023.GC2510@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Fri, 27 Jan 2012 15:10:23 -0500
> Here are a couple of "one-liner" fixes intended for 3.3.
>
> A mac80211 fix from Eliad Peller fixes a regression from an earlier
> patche that accidentally removed a necessary line of code. The other
> one from Eliad adds an overlooked assignment necessary for proper
> management of some state information. Finally, the fix from Johannes
> moves an unlock to include an additional operation within the critical
> section.
>
> Pleae let me know if there are problems!
Pulled, thanks John.
prev parent reply other threads:[~2012-01-28 1:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 20:10 pull request: wireless 2012-01-27 John W. Linville
2012-01-28 1:42 ` 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=20120127.204210.1693783796267469687.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).