mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Juergen Gross <jgross@suse.com>,
	Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xen/arm: Replace __ASSEMBLY__ with __ASSEMBLER__ in interface.h
Date: Wed, 22 Apr 2026 06:57:18 +0200	[thread overview]
Message-ID: <68b36ad0-2233-49d0-a3a6-bce053686bf1@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2604211513030.2712345@ubuntu-linux-20-04-desktop>

On 22/04/2026 00.15, Stefano Stabellini wrote:
> On Tue, 21 Apr 2026, Thomas Huth wrote:
>> From: Thomas Huth <thuth@redhat.com>
>>
>> While the GCC and Clang compilers already define __ASSEMBLER__
>> automatically when compiling assembly code, __ASSEMBLY__ is a
>> macro that only gets defined by the Makefiles in the kernel.
>> This can be very confusing when switching between userspace
>> and kernelspace coding, or when dealing with uapi headers that
>> rather should use __ASSEMBLER__ instead. So let's standardize now
>> on the __ASSEMBLER__ macro that is provided by the compilers.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
> 
> I haven't been closely following the __ASSEMBLER__ vs __ASSEMBLY__
> discussion. If there is general agreement to use __ASSEMBLER__ in
> headers, I am happy to go along with that. Currently, I see more than
> 140 uses of __ASSEMBLY__ compared to fewer than 20 uses of
> __ASSEMBLER__, but I'll defer to your judgment if the project is moving
> in that direction.

I assume you only counted the occurrences in the main include/ folder?
Please also take the arch/*/include/ folders into account:

thuth:~/devel/linux$ grep -r __ASSEMBLER__ arch/*/include/ | wc -l
1492
thuth:~/devel/linux$ grep -r __ASSEMBLY__ arch/*/include/ | wc -l
120

So most spots have been converted already. It would be great if you could 
help with the xen header!

  Thanks,
   Thomas


  reply	other threads:[~2026-04-22  4:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 14:27 Thomas Huth
2026-04-21 22:15 ` Stefano Stabellini
2026-04-22  4:57   ` Thomas Huth [this message]
2026-04-22  5:59 ` Jürgen Groß

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=68b36ad0-2233-49d0-a3a6-bce053686bf1@redhat.com \
    --to=thuth@redhat.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleksandr_tyshchenko@epam.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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 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®