All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: pull-request: mac80211 2013-03-22
Date: Mon, 25 Mar 2013 14:50:36 -0400	[thread overview]
Message-ID: <20130325185035.GA17454@tuxdriver.com> (raw)
In-Reply-To: <1364120480.9224.0.camel@jlt4.sipsolutions.net>

On Sun, Mar 24, 2013 at 11:21:20AM +0100, Johannes Berg wrote:
> *sigh*
> 
> 
> Testing found another issue. I'm not going to resend this, just give you
> a new commit ID.
> 
> > I have two tracing fixes (one from Vladimir), two fixes for P2P device
> > crashes, a fix for a BSS memory leak/lost update problem and a fix from
> > Ben for a scanning issue in mac80211. It's a little on the large side
> > because one of the P2P device problems required a bit much locking work,
> > but I've run through all the different scenarios (wext/nl80211,
> > p2p-device/station interface, ifdown/rfkill) to verify locking with
> > lockdep.
> 
> 
> 
> > The following changes since commit 801d929ca7d935ee199fd61d8ef914f51e892270:
> > 
> >   mac80211: another fix for idle handling in monitor mode (2013-03-02 21:24:42 +0100)
> > 
> > are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git for-john
> > 
> > for you to fetch changes up to 9e68a67a888d98bda8393c29dde12fb4f0b42a19:
> 
> Really 370bd005937c0e00f9104a602f9fe1dd6b21b54b now.

Pulling now (before you repost again!)...

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

      reply	other threads:[~2013-03-25 19:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 19:57 pull-request: mac80211 2013-03-19 Johannes Berg
2013-03-20 21:21 ` Johannes Berg
2013-03-22 10:19 ` pull-request: mac80211 2013-03-22 Johannes Berg
2013-03-24 10:21   ` Johannes Berg
2013-03-25 18:50     ` 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=20130325185035.GA17454@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.