[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bc3bc5ca-4000-43d6-9019-bae03c65d43c@ghiti.fr>
Date: Tue, 19 Aug 2025 22:17:08 +0200
From: Alexandre Ghiti <alex@...ti.fr>
To: Thomas Huth <thuth@...hat.com>, Alexandre Ghiti <alexghiti@...osinc.com>
Cc: linux-riscv@...ts.infradead.org, paul.walmsley@...ive.com,
palmer@...belt.com, aou@...s.berkeley.edu, atish.patra@...ux.dev,
anup@...infault.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] riscv: Replace __ASSEMBLY__ with __ASSEMBLER__ in
header files
Hi Thomas,
On 8/18/25 08:08, Thomas Huth wrote:
> On 06/08/2025 19.15, patchwork-bot+linux-riscv@...nel.org wrote:
>> Hello:
>>
>> This series was applied to riscv/linux.git (for-next)
>> by Alexandre Ghiti <alexghiti@...osinc.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?
No issues with the patches, Linus rejected the riscv PR. I'll send them
again for 6.18.
Sorry about that,
Alex
>
> 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!
>
Powered by blists - more mailing lists