All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@nvidia.com>
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, 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: Thu, 17 Apr 2025 08:30:47 +0300	[thread overview]
Message-ID: <aACSBy5o8yCuujTz@shredder> (raw)
In-Reply-To: <20250416200840.1338195-1-kuba@kernel.org>

On Wed, Apr 16, 2025 at 01:08:40PM -0700, Jakub Kicinski 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.
> 
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>

Reviewed-by: Ido Schimmel <idosch@nvidia.com>

  parent reply	other threads:[~2025-04-17  5:31 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 [this message]
2025-04-18  2:51 ` patchwork-bot+netdevbpf

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=aACSBy5o8yCuujTz@shredder \
    --to=idosch@nvidia.com \
    --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=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 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.