From: Jakub Kicinski <kuba@kernel.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: "open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>
Subject: Re: uapi-header: doesn't update header include guard macros
Date: Tue, 3 Oct 2023 14:45:13 -0700 [thread overview]
Message-ID: <20231003144513.1d6ed0e2@kernel.org> (raw)
In-Reply-To: <5AD3137D-F5F9-42E7-984C-4C82D2DB3C65@oracle.com>
On Fri, 15 Sep 2023 16:41:59 +0000 Chuck Lever III wrote:
> Hi Jakub-
>
> This is a minor nit, but I have
>
> name: xxxx
> uapi-header: linux/xxxx_netlink.h
>
> in my yaml spec, and the actual uapi file is named
>
> include/uapi/linux/xxxx_netlink.h
>
> but the generated include guard macros in that header still say:
>
> #ifndef _UAPI_LINUX_XXXX_H
> #define _UAPI_LINUX_XXXX_H
>
> ....
>
> #endif /* _UAPI_LINUX_XXXX_H */
>
> They should use _UAPI_LINUX_XXXX_NETLINK_H instead to avoid
> colliding with a human-written include/uapi/linux/xxxx.h.
Fair point, perhaps we can do something like the patch below.
LMK if it's good enough.
We don't have any family of this nature in the networking tree.
Would you need this for 6.7 i.e. the next merge window already?
I can put it on top of an -rc tag when applying, so you can merge..
----->8-----
diff --git a/tools/net/ynl/ynl-gen-c.py b/tools/net/ynl/ynl-gen-c.py
index 18532e78e1cf..168fe612b029 100755
--- a/tools/net/ynl/ynl-gen-c.py
+++ b/tools/net/ynl/ynl-gen-c.py
@@ -805,6 +805,10 @@ from lib import SpecFamily, SpecAttrSet, SpecAttr, SpecOperation, SpecEnumSet, S
self.uapi_header = self.yaml['uapi-header']
else:
self.uapi_header = f"linux/{self.name}.h"
+ if self.uapi_header.startswith("linux/") and self.uapi_header.endswith('.h'):
+ self.uapi_header_name = self.uapi_header[6:-2]
+ else:
+ self.uapi_header_name = self.name
def resolve(self):
self.resolve_up(super())
@@ -2124,7 +2128,7 @@ _C_KW = {
def render_uapi(family, cw):
- hdr_prot = f"_UAPI_LINUX_{family.uapi_header}_H"
+ hdr_prot = f"_UAPI_LINUX_{c_upper(family.uapi_header_name)}_H"
cw.p('#ifndef ' + hdr_prot)
cw.p('#define ' + hdr_prot)
cw.nl()
next prev parent reply other threads:[~2023-10-03 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 16:41 uapi-header: doesn't update header include guard macros Chuck Lever III
2023-10-03 21:45 ` Jakub Kicinski [this message]
2023-10-03 21:48 ` Jakub Kicinski
2023-10-03 22:47 ` Chuck Lever III
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=20231003144513.1d6ed0e2@kernel.org \
--to=kuba@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=netdev@vger.kernel.org \
/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.