From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, johannes@sipsolutions.net,
netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
jacob.e.keller@intel.com, fw@strlen.de, jiri@nvidia.com
Subject: Re: [PATCH net] genetlink: piggy back on resv_op to default to a reject policy
Date: Tue, 25 Oct 2022 02:20:15 +0000 [thread overview]
Message-ID: <166666441571.15570.13995760382513953418.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221021193532.1511293-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 21 Oct 2022 12:35:32 -0700 you wrote:
> To keep backward compatibility we used to leave attribute parsing
> to the family if no policy is specified. This becomes tedious as
> we move to more strict validation. Families must define reject all
> policies if they don't want any attributes accepted.
>
> Piggy back on the resv_start_op field as the switchover point.
> AFAICT only ethtool has added new commands since the resv_start_op
> was defined, and it has per-op policies so this should be a no-op.
>
> [...]
Here is the summary with links:
- [net] genetlink: piggy back on resv_op to default to a reject policy
https://git.kernel.org/netdev/net/c/4fa86555d1cd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-10-25 2:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 19:35 [PATCH net] genetlink: piggy back on resv_op to default to a reject policy Jakub Kicinski
2022-10-21 19:57 ` Johannes Berg
2022-10-22 4:08 ` Jakub Kicinski
2022-10-23 16:19 ` Johannes Berg
2022-10-24 10:00 ` Jacob Keller
2022-10-25 2:20 ` patchwork-bot+netdevbpf [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=166666441571.15570.13995760382513953418.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=jacob.e.keller@intel.com \
--cc=jiri@nvidia.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).