[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <5AD3137D-F5F9-42E7-984C-4C82D2DB3C65@oracle.com>
Date: Fri, 15 Sep 2023 16:41:59 +0000
From: Chuck Lever III <chuck.lever@...cle.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "open list:NETWORKING [GENERAL]" <netdev@...r.kernel.org>
Subject: uapi-header: doesn't update header include guard macros
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.
--
Chuck Lever
Powered by blists - more mailing lists