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-05-27
Date: Wed, 29 May 2013 14:52:30 -0400 [thread overview]
Message-ID: <20130529185229.GE8770@tuxdriver.com> (raw)
In-Reply-To: <1369660310.14740.12.camel@jlt4.sipsolutions.net>
On Mon, May 27, 2013 at 03:11:50PM +0200, Johannes Berg wrote:
> On Mon, 2013-05-27 at 14:42 +0200, Johannes Berg wrote:
> > John,
> >
> > I also have a bunch of new things for cfg80211/mac80211. Just like with
> > iwlwifi, I had to merge my mac80211 tree, so this pulled in some more
> > changes that looks spurious. Again, a better looking shortlog all the
> > way at the end.
> >
> > The biggest change this time is my cfg80211 locking and MLME/SME work,
> > cleaning up locking there by greatly reducing the number of different
> > useless locks. Other than that, some relatively minor things.
> >
> > Please let me know of any problems.
> >
> > johannes
> >
> >
> > The following changes since commit f722406faae2d073cc1d01063d1123c35425939e:
> >
> > Linux 3.10-rc1 (2013-05-11 17:14:08 -0700)
> >
> > 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 0dd83174762ff46356824217e69daf374f794ba4:
>
> Oh, there was a build error here, I've corrected it and the new HEAD is
> now 6abb9cb99f33b20c2f32f18a3ae9cc7543e46edb.
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-05-29 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 12:42 pull-request: mac80211-next 2013-05-27 Johannes Berg
2013-05-27 13:11 ` Johannes Berg
2013-05-29 18:52 ` 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=20130529185229.GE8770@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 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).