From: Andreas Larsson <andreas@gaisler.com>
To: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>,
linux-kernel@vger.kernel.org
Cc: sparclinux@vger.kernel.org,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Anthony Yznaga <anthony.yznaga@oracle.com>
Subject: Re: [PATCH 1/1] sparc: fix accurate exception reporting in copy_{from_to}_user for M7
Date: Thu, 4 Sep 2025 16:19:29 +0200 [thread overview]
Message-ID: <e06f1fba-cf85-4f12-ac1d-1c1b161da9b6@gaisler.com> (raw)
In-Reply-To: <20250828121844.2250-2-kernel@mkarcher.dialup.fu-berlin.de>
On 2025-08-28 14:18, Michael Karcher wrote:
> ---
> arch/sparc/lib/M7memcpy.S | 20 ++++++++++----------
> arch/sparc/lib/Memcpy_utils.S | 9 +++++++++
> 2 files changed, 19 insertions(+), 10 deletions(-)
I think putting this patch together with the first four in the v2 of the
"Fix accurate exception reporting in SPARC assembly" series would be
good so that they all are under the same cover letter that has the
larger context. A lore link in the v2 letter to both these v1 threads
would allow tracking back the discussion history for both threads.
Cheers,
Andreas
prev parent reply other threads:[~2025-09-04 14:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 12:18 sparc: Another fix for accurate exception reporting in copy_{from,to}_user Michael Karcher
2025-08-28 12:18 ` [PATCH 1/1] sparc: fix accurate exception reporting in copy_{from_to}_user for M7 Michael Karcher
2025-08-28 12:36 ` John Paul Adrian Glaubitz
2025-08-28 13:04 ` [PATCH v2 1/1] sparc: fix accurate exception reporting in copy_{from,to}_user " Michael Karcher
2025-08-31 23:43 ` John Paul Adrian Glaubitz
2025-09-01 7:00 ` Rainer Orth
2025-09-01 7:05 ` John Paul Adrian Glaubitz
2025-09-01 14:18 ` Rainer Orth
2025-09-01 19:15 ` John Paul Adrian Glaubitz
2025-09-04 14:19 ` Andreas Larsson [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=e06f1fba-cf85-4f12-ac1d-1c1b161da9b6@gaisler.com \
--to=andreas@gaisler.com \
--cc=anthony.yznaga@oracle.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=kernel@mkarcher.dialup.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
/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®