From: Jakub Kicinski <kuba@kernel•org>
To: Thorsten Leemhuis <linux@leemhuis•info>
Cc: davem@davemloft•net, netdev@vger•kernel.org, edumazet@google•com,
pabeni@redhat•com, andrew+netdev@lunn•ch, horms@kernel•org,
Kory Maincent <kory.maincent@bootlin•com>,
donald.hunter@gmail•com, jacob.e.keller@intel•com
Subject: Re: [PATCH net-next] tools: ynl: add missing header deps
Date: Wed, 23 Apr 2025 14:59:43 -0700 [thread overview]
Message-ID: <20250423145943.55479e70@kernel.org> (raw)
In-Reply-To: <59ba7a94-17b9-485f-aa6d-14e4f01a7a39@leemhuis.info>
On Wed, 23 Apr 2025 15:28:07 +0200 Thorsten Leemhuis wrote:
> Does anyone know why this problem occurs?
I typo'ed the inclusion guard :( Will send this shortly:
diff --git a/tools/net/ynl/Makefile.deps b/tools/net/ynl/Makefile.deps
index 8b7bf673b686..a5e6093903fb 100644
--- a/tools/net/ynl/Makefile.deps
+++ b/tools/net/ynl/Makefile.deps
@@ -27,7 +27,7 @@ CFLAGS_netdev:=$(call get_hdr_inc,_LINUX_NETDEV_H,netdev.h)
CFLAGS_nl80211:=$(call get_hdr_inc,__LINUX_NL802121_H,nl80211.h)
CFLAGS_nlctrl:=$(call get_hdr_inc,__LINUX_GENERIC_NETLINK_H,genetlink.h)
CFLAGS_nfsd:=$(call get_hdr_inc,_LINUX_NFSD_NETLINK_H,nfsd_netlink.h)
-CFLAGS_ovpn:=$(call get_hdr_inc,_LINUX_OVPN,ovpn.h)
+CFLAGS_ovpn:=$(call get_hdr_inc,_LINUX_OVPN_H,ovpn.h)
CFLAGS_ovs_datapath:=$(call get_hdr_inc,__LINUX_OPENVSWITCH_H,openvswitch.h)
CFLAGS_ovs_flow:=$(call get_hdr_inc,__LINUX_OPENVSWITCH_H,openvswitch.h)
prev parent reply other threads:[~2025-04-23 21:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 23:49 [PATCH net-next] tools: ynl: add missing header deps Jakub Kicinski
2025-04-19 1:13 ` Stanislav Fomichev
2025-04-19 8:48 ` Kory Maincent
2025-04-21 16:07 ` Keller, Jacob E
2025-04-22 9:10 ` patchwork-bot+netdevbpf
2025-04-23 13:28 ` Thorsten Leemhuis
2025-04-23 21:59 ` Jakub Kicinski [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=20250423145943.55479e70@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=donald.hunter@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=jacob.e.keller@intel$(echo .)com \
--cc=kory.maincent@bootlin$(echo .)com \
--cc=linux@leemhuis$(echo .)info \
--cc=netdev@vger$(echo .)kernel.org \
--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