From: Thomas Huth <thuth@redhat.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>,
"Nicolas Schier" <n.schier@fritz.com>
Cc: linux-kernel@vger.kernel.org, Nicolas Schier <nsc@kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Nick Huang <sef1548@gmail.com>,
linux-kbuild@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH] scripts: headers_install.sh: Normalize __ASSEMBLY__ to __ASSEMBLER__
Date: Wed, 22 Jul 2026 09:34:50 +0200 [thread overview]
Message-ID: <74311a07-afd1-46ff-b5e2-503de903366f@redhat.com> (raw)
In-Reply-To: <b83f2696-ec0e-4c35-98bf-1094588dfad1@t-8ch.de>
On 21/07/2026 23.32, Thomas Weißschuh wrote:
> On 2026-07-20 12:10:25+0200, Thomas Huth wrote:
>> From: Thomas Huth <thuth@redhat.com>
>>
>> A previous patch to headers_install.sh normalized the usage of
>> __ASSEMBLER__ to __ASSEMBLY__ in the UAPI headers due to the
>> assumption that older versions of GCC might not define __ASSEMBLER__
>> automatically and thus using __ASSEMBLER__ in the UAPI headers might
>> break compilation with very old versions of GCC. However, as we now
>> reassured, even GCC 2.95 still defines __ASSEMBLER__ automatically
>> (and even older versions are hopefully not in use with the current
>> Linux UAPI headers anymore).
>> __ASSEMBLER__ is also set automatically by other C compilers like PCC
>> (see https://github.com/IanHarvey/pcc/blob/cvs2git/2018.09.20/cc/cc/cc.1#L405)
>> and Tiny-C (see https://repo.or.cz/tinycc.git/commitdiff/a25325e9be13e52a),
>> so using __ASSEMBLER__ in UAPI header files should really be fine.
>
> I am not that happy about this explanation. The note about old GCC was
> dropped in the committed version of the patch.
> It should be enough to just explain why __ASSEMBLER__ is better.
Ok, I sent a v2 with an updated patch description, I hope that's better:
https://lore.kernel.org/lkml/20260722072928.24500-1-thuth@redhat.com/
If not, please provide a suggestion how it should look like.
Thanks,
Thomas
PS: Nicolas, I kept your Reviewed-by in v2 ... if you disagree with the
updated patch description, please complain there!
next prev parent reply other threads:[~2026-07-22 7:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 10:10 Thomas Huth
2026-07-21 11:14 ` Nicolas Schier
2026-07-21 20:54 ` Nathan Chancellor
2026-07-21 21:32 ` Thomas Weißschuh
2026-07-22 7:34 ` Thomas Huth [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-09 15:58 Thomas Weißschuh
2026-03-13 23:56 ` Nathan Chancellor
2026-03-24 17:05 ` Thomas Weißschuh
2026-03-24 18:35 ` Nathan Chancellor
2026-03-24 19:58 ` Thomas Weißschuh
2026-06-13 10:13 ` Nicolas Schier
2026-06-13 16:57 ` Nathan Chancellor
2026-07-16 10:24 ` Thomas Huth
2026-07-16 16:40 ` Thomas Weißschuh
2026-07-16 18:16 ` Maciej W. Rozycki
2026-07-17 15:25 ` Thomas Weißschuh
2026-07-20 15:31 ` Maciej W. Rozycki
2026-07-16 18:52 ` Thomas Huth
2026-07-17 15:28 ` Thomas Weißschuh
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=74311a07-afd1-46ff-b5e2-503de903366f@redhat.com \
--to=thuth@redhat.com \
--cc=arnd@arndb.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=n.schier@fritz.com \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=sef1548@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®