From: Richard Henderson <richard.henderson@linaro.org>
To: Taylor Simpson <tsimpson@quicinc.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: "Alessandro Di Federico" <ale@rev.ng>,
"Brian Cain" <bcain@quicinc.com>,
"alex.bennee@linaro.org" <alex.bennee@linaro.org>,
"bin.meng@windriver.com" <bin.meng@windriver.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"laurent@vivier.eu" <laurent@vivier.eu>,
"alistair.francis@wdc.com" <alistair.francis@wdc.com>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PULL 0/3] SIGSEGV fixes
Date: Fri, 23 Jul 2021 09:10:59 -1000 [thread overview]
Message-ID: <2ea78953-b060-cbf2-2dd2-11b200dab77e@linaro.org> (raw)
In-Reply-To: <BYAPR02MB48869717A65C396835F5BDD3DEE59@BYAPR02MB4886.namprd02.prod.outlook.com>
On 7/23/21 8:48 AM, Taylor Simpson wrote:
> I've added the riscv maintainers and Laurent and Alex to the CC list.
>
> Please advise on how to proceed. Is this a known issue with riscv? Should I try to debug the riscv target or remove the change to linux-test.c from the pull request?
Remove the linux-test.c from the pull request.
Someone will need to debug riscv, but I don't think you want that to block the bug fix for
hexagon.
r~
PS: Please use some subject-line indicator for what component you're patching. "SIGSEGV
fixes" is impossibly generic.
next prev parent reply other threads:[~2021-07-23 19:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 21:19 [PULL 0/3] SIGSEGV fixes Taylor Simpson
2021-07-21 21:19 ` [PULL 1/3] Hexagon (target/hexagon) remove put_user_*/get_user_* Taylor Simpson
2021-07-21 21:19 ` [PULL 2/3] target/hexagon: Drop include of qemu.h Taylor Simpson
2021-07-21 21:19 ` [PULL 3/3] linux-test (tests/tcg/multiarch/linux-test.c) add check Taylor Simpson
2021-07-22 17:31 ` [PULL 0/3] SIGSEGV fixes Peter Maydell
2021-07-23 18:48 ` Taylor Simpson
2021-07-23 19:10 ` Richard Henderson [this message]
2021-07-23 19:56 ` Philippe Mathieu-Daudé
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=2ea78953-b060-cbf2-2dd2-11b200dab77e@linaro.org \
--to=richard.henderson@linaro.org \
--cc=ale@rev.ng \
--cc=alex.bennee@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=bcain@quicinc.com \
--cc=bin.meng@windriver.com \
--cc=laurent@vivier.eu \
--cc=palmer@dabbelt.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tsimpson@quicinc.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).