From: sashiko-bot@kernel.org
To: "Thomas Huth" <thuth@redhat.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] sched: Replace __ASSEMBLY__ with __ASSEMBLER__ in sched.h header
Date: Tue, 22 Sep 2026 06:54:29 +0000 [thread overview]
Message-ID: <20260922065429.E43BB1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260922064641.61120-1-thuth@redhat.com>
> While the GCC and Clang compilers already define __ASSEMBLER__ auto-
> matically 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. Let's standardize now on the __ASSEMBLER__ macro to avoid
> this confusion.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260922064641.61120-1-thuth@redhat.com?part=1
prev parent reply other threads:[~2026-09-22 6:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 6:46 [PATCH] sched: Replace __ASSEMBLY__ with __ASSEMBLER__ in sched.h header Thomas Huth
2026-09-22 6:54 ` sashiko-bot [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=20260922065429.E43BB1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=thuth@redhat.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