From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: pull-request: mac80211-next 2013-06-03
Date: Mon, 3 Jun 2013 16:34:53 -0400 [thread overview]
Message-ID: <20130603203452.GI2727@tuxdriver.com> (raw)
In-Reply-To: <1370271087.8227.8.camel@jlt4.sipsolutions.net>
On Mon, Jun 03, 2013 at 04:51:27PM +0200, Johannes Berg wrote:
> John,
>
> Here's another small pull request for mac80211-next, I wanted to get a
> few fixes out. I have more stuff pending but not sure I can get that
> reviewed right away and don't want anyone waiting for the warning fix.
>
> I have two reverts for patches I accidentally merged in via a tree I
> shouldn't have merged and a the locking fix for the locking rework I
> did. On top of that, Felix's active monitor implementation, a patch to
> always send multicast on the CAB queue to avoid races and a small
> cleanup.
>
> johannes
>
>
> The following changes since commit 6abb9cb99f33b20c2f32f18a3ae9cc7543e46edb:
>
> cfg80211: make WoWLAN configuration available to drivers (2013-05-27 15:10:58 +0200)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git for-john
>
> for you to fetch changes up to ed405be5cb5e8e494e8dcd83b6eb1add34dc752a:
>
> mac80211: fix sdata locking around __ieee80211_request_smps (2013-06-03 13:51:59 +0200)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2013-06-03 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 14:51 pull-request: mac80211-next 2013-06-03 Johannes Berg
2013-06-03 20:34 ` John W. Linville [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=20130603203452.GI2727@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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.