From: WANG Xuerui <kernel@xen0n.name>
To: Huacai Chen <chenhuacai@kernel.org>, Xi Ruoyao <xry111@xry111.site>
Cc: loongarch@lists.linux.dev, WANG Xuerui <git@xen0n.name>,
Eric Biederman <ebiederm@xmission.com>,
Al Viro <viro@zeniv.linux.org.uk>, Arnd Bergmann <arnd@arndb.de>,
linux-api@vger.kernel.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] LoongArch: Make bounds-checking instructions useful
Date: Thu, 20 Apr 2023 17:38:49 +0800 [thread overview]
Message-ID: <2e8d357d-e006-bda8-3711-dcbafbd4c53e@xen0n.name> (raw)
In-Reply-To: <CAAhV-H7zTjSsz=e+0r-9Z0KOF-Gxr-chXnVgWo+4eNA1ptWw1g@mail.gmail.com>
On 2023/4/20 16:36, Huacai Chen wrote:
> Hi, Xuerui,
>
> I hope V2 can be applied cleanly without the patch series "LoongArch:
> Better backtraces", thanks.
I believe it's already the case (just try; I've moved the BADV printing
for BCE into the better backtraces series before sending this).
I'm only waiting for comments from the other UAPI maintainers on the CC
list.
--
WANG "xen0n" Xuerui
Linux/LoongArch mailing list: https://lore.kernel.org/loongarch/
next prev parent reply other threads:[~2023-04-20 9:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 17:33 [PATCH 0/2] LoongArch: Make bounds-checking instructions useful WANG Xuerui
2023-04-16 17:33 ` [PATCH 1/2] LoongArch: Add opcodes of bounds-checking instructions WANG Xuerui
2023-04-16 17:33 ` [PATCH 2/2] LoongArch: Relay BCE exceptions to userland as SIGSEGVs with si_code=SEGV_BNDERR WANG Xuerui
2023-04-16 17:57 ` WANG Xuerui
2023-04-17 6:47 ` [PATCH 0/2] LoongArch: Make bounds-checking instructions useful Xi Ruoyao
2023-04-17 7:54 ` WANG Xuerui
2023-04-17 9:50 ` Xi Ruoyao
2023-04-20 8:36 ` Huacai Chen
2023-04-20 9:38 ` WANG Xuerui [this message]
2023-04-22 8:39 ` Huacai Chen
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=2e8d357d-e006-bda8-3711-dcbafbd4c53e@xen0n.name \
--to=kernel@xen0n.name \
--cc=arnd@arndb.de \
--cc=chenhuacai@kernel.org \
--cc=ebiederm@xmission.com \
--cc=git@xen0n.name \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
--cc=xry111@xry111.site \
/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).