From: Jiri Pirko <jiri@resnulli•us>
To: Jakub Kicinski <kuba@kernel•org>
Cc: davem@davemloft•net, netdev@vger•kernel.org, edumazet@google•com,
pabeni@redhat•com, Nicolas Dichtel <nicolas.dichtel@6wind•com>,
chuck.lever@oracle•com
Subject: Re: [PATCH net-next] tools: ynl: fix header guards
Date: Fri, 23 Feb 2024 10:02:55 +0100 [thread overview]
Message-ID: <ZdhfP3lMccJC6KFB@nanopsycho> (raw)
In-Reply-To: <20240222234831.179181-1-kuba@kernel.org>
Fri, Feb 23, 2024 at 12:48:31AM CET, kuba@kernel•org wrote:
>devlink and ethtool have a trailing _ in the header guard. I must have
>copy/pasted it into new guards, assuming it's a headers_install artifact.
>
>This fixes build if system headers are old.
>
>Fixes: 8f109e91b852 ("tools: ynl: include dpll and mptcp_pm in C codegen")
>Acked-by: Nicolas Dichtel <nicolas.dichtel@6wind•com>
>Signed-off-by: Jakub Kicinski <kuba@kernel•org>
Reviewed-by: Jiri Pirko <jiri@nvidia•com>
next prev parent reply other threads:[~2024-02-23 9:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 23:48 [PATCH net-next] tools: ynl: fix header guards Jakub Kicinski
2024-02-23 9:02 ` Jiri Pirko [this message]
2024-02-24 3:10 ` 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=ZdhfP3lMccJC6KFB@nanopsycho \
--to=jiri@resnulli$(echo .)us \
--cc=chuck.lever@oracle$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nicolas.dichtel@6wind$(echo .)com \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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