Re: [PATCH v2 0/2] riscv: Replace __ASSEMBLY__ with __ASSEMBLER__ in header files

From: Thomas Huth <thuth@redhat.com>
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	atish.patra@linux.dev, anup@brainfault.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] riscv: Replace __ASSEMBLY__ with __ASSEMBLER__ in header files
Date: Mon, 18 Aug 2025 08:08:54 +0200	[thread overview]
Message-ID: <d1fe7fdf-b3da-4c53-8a5a-a87acd38d525@redhat.com> (raw)
In-Reply-To: <175450055499.2863135.2738368758577957268.git-patchwork-notify@kernel.org>

On 06/08/2025 19.15, patchwork-bot+linux-riscv@kernel.org wrote:
> Hello:
> 
> This series was applied to riscv/linux.git (for-next)
> by Alexandre Ghiti <alexghiti@rivosinc.com>:

  Hi Alexandre,

I can't see the patches in the for-next branch ... have they been dropped 
again? Was there an issue with the patches?

  Thanks,
   Thomas

> On Fri,  6 Jun 2025 09:09:50 +0200 you wrote:
>> The kernel Makefiles define the __ASSEMBLY__ macro to provide
>> a way to use headers in both, assembly and C source code.
>> However, all the supported versions of the GCC and Clang compilers
>> also define the macro __ASSEMBLER__ automatically already when compiling
>> assembly code, so some kernel headers are using __ASSEMBLER__ instead.
>> With regards to userspace code, this seems also to be constant source
>> of confusion, see for example these links here:
>>
>> [...]
> 
> Here is the summary with links:
>    - [v2,1/2] riscv: Replace __ASSEMBLY__ with __ASSEMBLER__ in uapi headers
>      https://git.kernel.org/riscv/c/c47963980ba6
>    - [v2,2/2] riscv: Replace __ASSEMBLY__ with __ASSEMBLER__ in non-uapi headers
>      https://git.kernel.org/riscv/c/b5eb1f12a416
> 
> You are awesome, thank you!

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv