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,
m.grzeschik@pengutronix.de, jv@jvosburgh.net,
willemdebruijn.kernel@gmail.com, magnus.karlsson@intel.com,
maciej.fijalkowski@intel.com, nhorman@tuxdriver.com,
kernelxing@tencent.com, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us, idosch@nvidia.com,
gnault@redhat.com, petrm@nvidia.com, bpf@vger.kernel.org
Subject: Re: [PATCH net-next] net: add UAPI to the header guard in various network headers
Date: Fri, 18 Apr 2025 02:51:03 +0000 [thread overview]
Message-ID: <174494466324.88264.13705902827230140149.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250416200840.1338195-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 16 Apr 2025 13:08:40 -0700 you wrote:
> fib_rule, ip6_tunnel, and a whole lot of if_* headers lack the customary
> _UAPI in the header guard. Without it YNL build can't protect from in tree
> and system headers both getting included. YNL doesn't need most of these
> but it's annoying to have to fix them one by one.
>
> Note that header installation strips this _UAPI prefix so this should
> result in no change to the end user.
>
> [...]
Here is the summary with links:
- [net-next] net: add UAPI to the header guard in various network headers
https://git.kernel.org/netdev/net-next/c/8066e388be48
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-04-18 2:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 20:08 [PATCH net-next] net: add UAPI to the header guard in various network headers Jakub Kicinski
2025-04-16 22:18 ` Jamal Hadi Salim
2025-04-17 1:11 ` Jason Xing
2025-04-17 5:30 ` Ido Schimmel
2025-04-18 2:51 ` 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=174494466324.88264.13705902827230140149.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=jv@jvosburgh.net \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=m.grzeschik@pengutronix.de \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xiyou.wangcong@gmail.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).