From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: <linux-arm-kernel@lists.infradead.org>,
Tong Tiangen <tongtiangen@huawei.com>
Subject: Re: [PATCH v11 1/5] uaccess: add generic fallback version of copy_mc_to_user()
Date: Thu, 8 Feb 2024 13:39:58 +0000 [thread overview]
Message-ID: <20240208133958.00004002@Huawei.com> (raw)
In-Reply-To: <20240208133818.000009ea@Huawei.com>
On Thu, 8 Feb 2024 13:38:18 +0000
Jonathan Cameron <Jonathan.Cameron@Huawei.com> wrote:
> On Wed, 7 Feb 2024 21:22:00 +0800
> Tong Tiangen <tongtiangen@huawei.com> wrote:
>
> > x86/powerpc has it's implementation of copy_mc_to_user(), we add generic
> > fallback in include/linux/uaccess.h prepare for other architechures to
> architectures
>
> (only bother fixing if you end up doing a v12 - hence off list reply!)
gah. Email mess up and I missed the cancel button.
Anyhow, harmless feedback ;)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-08 13:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 13:21 [PATCH v11 0/5]arm64: add ARCH_HAS_COPY_MC support Tong Tiangen
2024-02-07 13:22 ` [PATCH v11 1/5] uaccess: add generic fallback version of copy_mc_to_user() Tong Tiangen
2024-02-08 13:38 ` Jonathan Cameron
2024-02-08 13:39 ` Jonathan Cameron [this message]
2024-02-07 13:22 ` [PATCH v11 2/5] arm64: add support for ARCH_HAS_COPY_MC Tong Tiangen
2024-02-07 13:22 ` [PATCH v11 3/5] mm/hwpoison: return -EFAULT when copy fail in copy_mc_[user]_highpage() Tong Tiangen
2024-02-07 13:22 ` [PATCH v11 4/5] arm64: support copy_mc_[user]_highpage() Tong Tiangen
2024-02-07 13:22 ` [PATCH v11 5/5] arm64: send SIGBUS to user process for SEA exception Tong Tiangen
2024-02-18 7:05 ` [PATCH v11 0/5]arm64: add ARCH_HAS_COPY_MC support Tong Tiangen
2024-03-27 0:49 ` Tong Tiangen
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=20240208133958.00004002@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=tongtiangen@huawei.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).