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: pull-request: mac80211 2013-07-26
Date: Fri, 26 Jul 2013 10:42:33 +0200	[thread overview]
Message-ID: <1374828153.8248.19.camel@jlt4.sipsolutions.net> (raw)

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

John,

And another one for mac80211 - that's all for now then :-)

I only have three fixes this time, a fix for a suspend regression, a
patch correcting the initiator in regulatory code and one fix for mesh
station powersave.

Let me know if there's any problem.

johannes


The following changes since commit 5c9fc93bc9bc417418fc1b6366833ae6a07b804d:

  mac80211/minstrel: fix NULL pointer dereference issue (2013-07-16 17:48:14 +0300)

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 23df0b731954502a9391e739b92927cee4360343:

  regulatory: use correct regulatory initiator on wiphy register (2013-07-25 09:52:46 +0200)

----------------------------------------------------------------
Arik Nemtsov (1):
      regulatory: use correct regulatory initiator on wiphy register

Chun-Yeow Yeoh (1):
      mac80211: prevent the buffering or frame transmission to non-assoc mesh STA

Stanislaw Gruszka (1):
      mac80211: fix monitor interface suspend crash regression

 net/mac80211/mesh_ps.c | 4 ++++
 net/mac80211/pm.c      | 7 +++++--
 net/wireless/reg.c     | 5 ++++-
 3 files changed, 13 insertions(+), 3 deletions(-)


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

             reply	other threads:[~2013-07-26  8:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26  8:42 Johannes Berg [this message]
2013-07-29 18:48 ` pull-request: mac80211 2013-07-26 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=1374828153.8248.19.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).