From: Catalin Marinas <catalin.marinas@arm.com>
To: Julian Vetter <jvetter@kalrayinc.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Will Deacon <will@kernel.org>,
Guo Ren <guoren@kernel.org>, Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
Andrew Morton <akpm@linux-foundation.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-csky@vger.kernel.org,
loongarch@lists.linux.dev,
Yann Sionneau <ysionneau@kalrayinc.com>
Subject: Re: [PATCH v5 3/5] Use generic io memcpy functions on the arm64 architecture
Date: Tue, 24 Sep 2024 16:40:32 +0100 [thread overview]
Message-ID: <ZvLdcGesj-gMANyR@arm.com> (raw)
In-Reply-To: <20240924121432.798655-4-jvetter@kalrayinc.com>
On Tue, Sep 24, 2024 at 02:14:30PM +0200, Julian Vetter wrote:
> Use the generic __memcpy_{from,to}io and __memset_io functions on the
> arm64 processor architecture.
>
> Reviewed-by: Yann Sionneau <ysionneau@kalrayinc.com>
> Signed-off-by: Julian Vetter <jvetter@kalrayinc.com>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
And a nitpick if you respin: we tend to write the subject as arch name,
colon followed by the actual text. E.g.:
arm64: Use generic io memcpy functions
next prev parent reply other threads:[~2024-09-24 15:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 12:14 [PATCH v5 0/5] Consolidate IO memcpy functions Julian Vetter
2024-09-24 12:14 ` [PATCH v5 1/5] Consolidate __memcpy_{to,from}io and __memset_io into iomap_copy.c Julian Vetter
2024-09-24 21:36 ` kernel test robot
2024-09-24 22:48 ` kernel test robot
2024-09-25 1:01 ` kernel test robot
2024-09-24 12:14 ` [PATCH v5 2/5] Replace generic memcpy and memset by IO memcpy functions Julian Vetter
2024-09-24 12:14 ` [PATCH v5 3/5] Use generic io memcpy functions on the arm64 architecture Julian Vetter
2024-09-24 15:40 ` Catalin Marinas [this message]
2024-09-24 12:14 ` [PATCH v5 4/5] Use generic io memcpy functions on the csky architecture Julian Vetter
2024-09-24 12:14 ` [PATCH v5 5/5] Use generic io memcpy functions on the loongarch architecture Julian Vetter
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=ZvLdcGesj-gMANyR@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=chenhuacai@kernel.org \
--cc=guoren@kernel.org \
--cc=jvetter@kalrayinc.com \
--cc=kernel@xen0n.name \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=will@kernel.org \
--cc=ysionneau@kalrayinc.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;
as well as URLs for NNTP newsgroup(s).