From: Will Deacon <will@kernel.org>
To: linux@armlinux.org.uk, catalin.marinas@arm.com, chris@zankel.net,
jcmvbkbc@gmail.com, ldv@strace.io, charlie@rivosinc.com,
deller@gmx.de, macro@orcam.me.uk, akpm@linux-foundation.org,
mark.rutland@arm.com, rostedt@goodmis.org, tglx@linutronix.de,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Jinjie Ruan <ruanjinjie@huawei.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>
Subject: Re: [PATCH v2 0/2] syscall: Cleanup and improve syscall_get_arguments()
Date: Mon, 5 Jan 2026 22:58:27 +0000 [thread overview]
Message-ID: <176763166882.1385538.15950355888937561559.b4-ty@kernel.org> (raw)
In-Reply-To: <20251201120633.1193122-1-ruanjinjie@huawei.com>
On Mon, 01 Dec 2025 20:06:31 +0800, Jinjie Ruan wrote:
> Remove unused SYSCALL_MAX_ARGS and avoid memcpy() for
> syscall_get_arguments() for arm64.
>
> Jinjie Ruan (2):
> syscall.h: Remove unused SYSCALL_MAX_ARGS
> arm64: Avoid memcpy() for syscall_get_arguments()
>
> [...]
Applied to arm64 (for-next/entry), thanks!
[1/2] syscall.h: Remove unused SYSCALL_MAX_ARGS
https://git.kernel.org/arm64/c/35c3dcb1ac2c
[2/2] arm64: Avoid memcpy() for syscall_get_arguments()
https://git.kernel.org/arm64/c/98cc091262ef
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-01-05 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 12:06 Jinjie Ruan
2025-12-01 12:06 ` [PATCH v2 1/2] syscall.h: Remove unused SYSCALL_MAX_ARGS Jinjie Ruan
2025-12-01 15:24 ` Russell King (Oracle)
2025-12-01 12:06 ` [PATCH v2 2/2] arm64: Avoid memcpy() for syscall_get_arguments() Jinjie Ruan
2026-01-05 22:58 ` Will Deacon [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=176763166882.1385538.15950355888937561559.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=charlie@rivosinc.com \
--cc=chris@zankel.net \
--cc=deller@gmx.de \
--cc=jcmvbkbc@gmail.com \
--cc=kernel-team@android.com \
--cc=ldv@strace.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=macro@orcam.me.uk \
--cc=mark.rutland@arm.com \
--cc=rostedt@goodmis.org \
--cc=ruanjinjie@huawei.com \
--cc=tglx@linutronix.de \
/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®