From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
cjubran@nvidia.com, donald.hunter@gmail.com,
nicolas.dichtel@6wind.com
Subject: Re: [PATCH net-next 1/2] tools: ynl-gen: don't output external constants
Date: Thu, 06 Feb 2025 10:40:32 +0000 [thread overview]
Message-ID: <173883843252.1427982.13885311367700150420.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250203215510.1288728-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 3 Feb 2025 13:55:09 -0800 you wrote:
> A definition with a "header" property is an "external" definition
> for C code, as in it is defined already in another C header file.
> Other languages will need the exact value but C codegen should
> not recreate it. So don't output those definitions in the uAPI
> header.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>
> [...]
Here is the summary with links:
- [net-next,1/2] tools: ynl-gen: don't output external constants
https://git.kernel.org/netdev/net-next/c/7e8b24e24ac4
- [net-next,2/2] tools: ynl-gen: support limits using definitions
https://git.kernel.org/netdev/net-next/c/fa796178e5eb
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:[~2025-02-06 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 21:55 [PATCH net-next 1/2] tools: ynl-gen: don't output external constants Jakub Kicinski
2025-02-03 21:55 ` [PATCH net-next 2/2] tools: ynl-gen: support limits using definitions Jakub Kicinski
2025-02-06 10:40 ` 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=173883843252.1427982.13885311367700150420.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=cjubran@nvidia.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.