Received-SPF: pass (google.com: domain of linux-kernel+bounces-168139-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Feedback-ID: i56a14606:Fastmail
User-Agent: Cyrus-JMAP/3.11.0-alpha0-417-gddc99d37d-fm-hotfix-20240424.001-g2c179674
Precedence: bulk
MIME-Version: 1.0
Message-Id: <cb22252d-1ea9-4094-9f7a-b94c2142d1f2@app.fastmail.com>
In-Reply-To: <ZjUzt3Rysyk-oGdQ@smile.fi.intel.com>
References: <ZjUzt3Rysyk-oGdQ@smile.fi.intel.com>
Date: Fri, 03 May 2024 21:34:13 +0200
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
 "David Howells" <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: compiler_types.h in UAPI?
Content-Type: text/plain

On Fri, May 3, 2024, at 20:57, Andy Shevchenko wrote:
> Hi!
>
> Today I have stumbled over use of __force and other compiler_types.h related
> things in UAPI headers. Can anybody explain to me how do they suppose to work
> outside of the kernel? Or did I miss something obvious? Or it was a mistake
> during UAPI split to move swab.h and byteorder/ (most of the users of those)
> to UAPI in the first place?

These get stripped out by scripts/headers_install.sh during
the 'make headers_install' stage:

sed -E -e '
        s/([[:space:](])(__user|__force|__iomem)[[:space:]]/\1/g
        s/__attribute_const__([[:space:]]|$)/\1/g
        s@^#include <linux/compiler(|_types).h>@@
        s/(^|[^a-zA-Z0-9])__packed([^a-zA-Z0-9_]|$)/\1__attribute__((packed))\2/g
        s/(^|[[:space:](])(inline|asm|volatile)([[:space:](]|$)/\1__\2__\3/g
        s@#(ifndef|define|endif[[:space:]]*/[*])[[:space:]]*_UAPI@#\1 @
' $INFILE > $TMPFILE || exit 1


      Arnd