From: Nick Huang <sef1548@gmail.com>
To: macro@orcam.me.uk
Cc: davidgow@google.com, dongsheng.yang@linux.dev,
dory85109@gmail.com, ebiggers@kernel.org, idryomov@gmail.com,
jlayton@kernel.org, john.g.garry@oracle.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
namhyung@kernel.org, robh@kernel.org, sef1548@gmail.com,
wdhh6@aliyun.com, wqu@suse.com, yot4106@gmail.com,
likerockman102@hotmail.com, squid@squidspirit.com
Subject: Re: [PATCH] arm: Replace __ASSEMBLY__ with __ASSEMBLER__ in uapi headers
Date: Fri, 27 Feb 2026 18:53:35 +0000 [thread overview]
Message-ID: <20260227185339.4187-1-sef1548@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2602190008470.57399@angie.orcam.me.uk>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=yes, Size: 735 bytes --]
> While not a regression, as this used not to work anyway with ASSEMBLY,
> the use of ASSEMBLER requires sufficiently new a compiler and in principle
> the userland may have old tools installed for whatever reason. So perhaps
> #error is in order if the compiler is not recent enough, for a complete
> fix?
> FWIW GCC 2.95.x didn't yet have it, it landed ultimately with GCC 3.0.
> Do we care? For instance the GNU C library still does for its installed
> headers.
>
> Maciej
Thanks, Maciej — good point about older toolchains. I'll send v2 of the patch that adds a compile-time check and an #error when the
compiler is too old to provide ASSEMBLER, making the failure explicit.
--
Regards,
Nick Huang
prev parent reply other threads:[~2026-02-27 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 13:39 [PATCH] arm: Replace ASSEMBLY with ASSEMBLER in uapi headers Nick Huang
2026-02-19 0:22 ` Maciej W. Rozycki
2026-02-27 18:53 ` Nick Huang [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=20260227185339.4187-1-sef1548@gmail.com \
--to=sef1548@gmail.com \
--cc=davidgow@google.com \
--cc=dongsheng.yang@linux.dev \
--cc=dory85109@gmail.com \
--cc=ebiggers@kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=john.g.garry@oracle.com \
--cc=likerockman102@hotmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=macro@orcam.me.uk \
--cc=namhyung@kernel.org \
--cc=robh@kernel.org \
--cc=squid@squidspirit.com \
--cc=wdhh6@aliyun.com \
--cc=wqu@suse.com \
--cc=yot4106@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