From: patchwork-bot+netdevbpf@kernel.org
To: Antonio Quartulli <a@unstable.cc>
Cc: donald.hunter@gmail.com, kuba@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] ynl: ensure exact-len value is resolved
Date: Mon, 13 May 2024 22:50:28 +0000 [thread overview]
Message-ID: <171564062893.28873.1783841297383261530.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240510232202.24051-1-a@unstable.cc>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 11 May 2024 01:22:02 +0200 you wrote:
> For type String and Binary we are currently usinig the exact-len
> limit value as is without attempting any name resolution.
> However, the spec may specify the name of a constant rather than an
> actual value, which would result in using the constant name as is
> and thus break the policy.
>
> Ensure the limit value is passed to get_limit(), which will always
> attempt resolving the name before printing the policy rule.
>
> [...]
Here is the summary with links:
- ynl: ensure exact-len value is resolved
https://git.kernel.org/netdev/net-next/c/ec8c25746e32
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:[~2024-05-13 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 23:22 [PATCH] ynl: ensure exact-len value is resolved Antonio Quartulli
2024-05-13 22:50 ` 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=171564062893.28873.1783841297383261530.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a@unstable.cc \
--cc=donald.hunter@gmail.com \
--cc=kuba@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 read-only IMAP folder(s) and NNTP newsgroup(s).