From: Jakub Kicinski <kuba@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
kvalo@codeaurora.org
Subject: Re: [PATCH wireless 0/3] nl80211: add missing attribute validation
Date: Tue, 3 Mar 2020 09:53:32 -0800 [thread overview]
Message-ID: <20200303095332.138ce9b7@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <e5d88e0dbca9cc445caa95cfe32edda52f6b193d.camel@sipsolutions.net>
On Tue, 03 Mar 2020 08:29:46 +0100 Johannes Berg wrote:
> Hi Jakub,
>
> > Wireless seems to be missing a handful of netlink policy entries.
>
> Yep, these look good to me.
>
> Here's a
>
> Reviewed-by: Johannes Berg <johannes@sipsolutions.net>
>
> if you want to apply them directly?
Up to Dave, I only put a maintainer hat to cover for Dave when he's
away :)
> I can take them, but you said later you might want to pick them into
> stable, so maybe you have some more direct plan there?
No real plan, but the autoselection bot will very likely pick those up
even if we don't do anything, so given the very limited testing I was
cautious with refactoring.
next prev parent reply other threads:[~2020-03-03 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 5:10 [PATCH wireless 0/3] nl80211: add missing attribute validation Jakub Kicinski
2020-03-03 5:10 ` [PATCH wireless 1/3] nl80211: add missing attribute validation for critical protocol indication Jakub Kicinski
2020-03-03 5:10 ` [PATCH wireless 2/3] nl80211: add missing attribute validation for beacon report scanning Jakub Kicinski
2020-03-03 5:10 ` [PATCH wireless 3/3] nl80211: add missing attribute validation for channel switch Jakub Kicinski
2020-03-03 7:29 ` [PATCH wireless 0/3] nl80211: add missing attribute validation Johannes Berg
2020-03-03 17:53 ` Jakub Kicinski [this message]
2020-03-03 18:58 ` Johannes Berg
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=20200303095332.138ce9b7@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=kvalo@codeaurora.org \
--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).