mbox series

pull-request: mac80211 2019-04-26

Message ID 20190426090747.20949-1-johannes@sipsolutions.net (mailing list archive)
State Not Applicable
Delegated to: Johannes Berg
Headers show
Series pull-request: mac80211 2019-04-26 | expand

Pull-request

git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git tags/mac80211-for-davem-2019-04-26

Message

Johannes Berg April 26, 2019, 9:07 a.m. UTC
Hi Dave,

Just have a few more stragglers, looks like things have quieted down.

Please pull and let me know if there's any problem.

Thanks,
johannes



The following changes since commit c03fd0171ba6c8807ff5ba7c797896c84e18f3bc:

  Merge tag 'mac80211-for-davem-2019-04-09' of git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211 (2019-04-09 10:57:10 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git tags/mac80211-for-davem-2019-04-26

for you to fetch changes up to 517879147493a5e1df6b89a50f708f1133fcaddb:

  mac80211: don't attempt to rename ERR_PTR() debugfs dirs (2019-04-23 13:47:05 +0200)

----------------------------------------------------------------
 * fix use-after-free in mac80211 TXQs
 * fix RX STBC byte order
 * fix debugfs rename crashing due to ERR_PTR()
 * fix missing regulatory notification

----------------------------------------------------------------
Bhagavathi Perumal S (1):
      mac80211: Fix kernel panic due to use of txq after free

Johannes Berg (2):
      mac80211: fix RX STBC override byte order
      mac80211: don't attempt to rename ERR_PTR() debugfs dirs

Sriram R (1):
      cfg80211: Notify previous user request during self managed wiphy registration

 net/mac80211/debugfs_netdev.c | 2 +-
 net/mac80211/ht.c             | 5 +++--
 net/mac80211/iface.c          | 3 +++
 net/wireless/reg.c            | 5 ++---
 4 files changed, 9 insertions(+), 6 deletions(-)

Comments

Johannes Berg April 29, 2019, 11:19 a.m. UTC | #1
Hi Dave,

Sorry to nag, and maybe I'm missing something, but I didn't see this
show up in your tree, yet you marked it as accepted in patchwork:

https://patchwork.ozlabs.org/patch/1091413/

But maybe there's a gap that I should expect here, like you mark it as
accepted when you start some kind of testing and then push it out later?

Really the only reason I'm asking is that I wanted to forward to apply
another patch, but maybe I'll ask you to apply that one patch directly.

Thanks,
johannes
David Miller April 29, 2019, 3:02 p.m. UTC | #2
From: Johannes Berg <johannes@sipsolutions.net>
Date: Mon, 29 Apr 2019 13:19:27 +0200

> Sorry to nag, and maybe I'm missing something, but I didn't see this
> show up in your tree, yet you marked it as accepted in patchwork:
> 
> https://patchwork.ozlabs.org/patch/1091413/
> 
> But maybe there's a gap that I should expect here, like you mark it as
> accepted when you start some kind of testing and then push it out later?
> 
> Really the only reason I'm asking is that I wanted to forward to apply
> another patch, but maybe I'll ask you to apply that one patch directly.

Sorry about that, I'll use the excuse that I'm travelling :-)

I've pulled it in now and pushed it back out, should certainly be
there for sure now.