From: Johannes Berg <johannes@sipsolutions.net>
To: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: pull-request: mac80211 2021-04-08
Date: Thu, 08 Apr 2021 16:42:10 +0200 [thread overview]
Message-ID: <f37b7a2e1f6e0348799fa3dfd0845e67fa0ebd81.camel@sipsolutions.net> (raw)
In-Reply-To: <20210408125344.50279-1-johannes@sipsolutions.net> (sfid-20210408_145352_855056_807E3D7B)
On Thu, 2021-04-08 at 14:53 +0200, Johannes Berg wrote:
> Hi,
>
> Yes, I'm late with this, sorry about that. I've mostly restricted this
> to the most necessary fixes, though the virt_wifi one isn't but since
> that's not used a lot, it's harmless and included since it's obvious.
>
> The only thing that's bigger is the rfkill thing, but that's just since
> it adds a new version of the struct for userspace to use, since the
> change to the existing struct caused various breakage all around.
Wait, let me withdraw that - I have another syzbot fix coming.
johannes
prev parent reply other threads:[~2021-04-08 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 12:53 pull-request: mac80211 2021-04-08 Johannes Berg
2021-04-08 14:42 ` Johannes Berg [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=f37b7a2e1f6e0348799fa3dfd0845e67fa0ebd81.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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).