linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: pull-request: mac80211 2013-03-22
Date: Fri, 22 Mar 2013 11:19:31 +0100	[thread overview]
Message-ID: <1363947571.8238.4.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1363723052.8336.6.camel@jlt4.sipsolutions.net> (sfid-20130319_205755_751711_D4ADDEEC)

[-- Attachment #1: Type: text/plain, Size: 2235 bytes --]

Hi John,

Now I'm reviving this pull-request :-)

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.

Let me know if there's any problem.

johannes


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:

  mac80211: Don't restart sta-timer if not associated. (2013-03-22 10:55:55 +0100)

----------------------------------------------------------------
Ben Greear (1):
      mac80211: Don't restart sta-timer if not associated.

Johannes Berg (6):
      mac80211: always synchronize_net() during station removal
      cfg80211: fix potential BSS memory leak and update
      mac80211: fix crash with P2P Device returning action frames
      cfg80211: fix wdev tracing crash
      mac80211: fix virtual monitor interface locking
      cfg80211: always check for scan end on P2P device

Vladimir Kondratiev (1):
      cfg80211: fix inconsistency in trace for rdev_set_mac_acl

 net/mac80211/iface.c    | 35 ++++++++++++++++--------------
 net/mac80211/mesh.c     |  3 ++-
 net/mac80211/mlme.c     |  6 ++++--
 net/mac80211/rx.c       | 14 +++++++++++-
 net/mac80211/sta_info.c | 12 +++++++++--
 net/wireless/core.c     | 57 ++++++++++++++++++++++++++++++++++++-------------
 net/wireless/core.h     |  3 +++
 net/wireless/nl80211.c  | 52 ++++++++++++++++++++++----------------------
 net/wireless/scan.c     | 24 ++++++++++++++-------
 net/wireless/sme.c      |  6 ++++--
 net/wireless/trace.h    |  5 +++--
 net/wireless/wext-sme.c |  6 ++++++
 12 files changed, 149 insertions(+), 74 deletions(-)


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  parent reply	other threads:[~2013-03-22 10:19 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 ` Johannes Berg [this message]
2013-03-24 10:21   ` pull-request: mac80211 2013-03-22 Johannes Berg
2013-03-25 18:50     ` John W. Linville

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=1363947571.8238.4.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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).