From: <Conor.Dooley@microchip.com>
To: <chenguokai17@mails.ucas.ac.cn>
Cc: <paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
<aou@eecs.berkeley.edu>, <rostedt@goodmis.org>,
<mingo@redhat.com>, <sfr@canb.auug.org.au>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<liaochang1@huawei.com>
Subject: Re: [PATCH] arch/riscv: kprobes: implement optprobes
Date: Wed, 31 Aug 2022 08:15:31 +0000 [thread overview]
Message-ID: <999df577-48bd-6ffb-a868-cad8ba4615a1@microchip.com> (raw)
In-Reply-To: <DC2CEC17-4895-4060-B64A-7A444633F5F1@mails.ucas.ac.cn>
On 31/08/2022 08:48, Xim wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> Hi Conor,
>
> Thanks for your review! I will correct addressed issues in the next version. I have some explanations for others.
FYI, this mail arrived as html so will not get processed by the
mailing lists.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-08-31 8:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 4:10 [PATCH] arch/riscv: kprobes: implement optprobes Chen Guokai
2022-08-31 7:24 ` Conor.Dooley
2022-08-31 7:49 ` liaochang (A)
2022-08-31 7:52 ` Conor.Dooley
2022-08-31 8:28 ` liaochang (A)
2022-08-31 7:51 ` Conor.Dooley
[not found] ` <DC2CEC17-4895-4060-B64A-7A444633F5F1@mails.ucas.ac.cn>
2022-08-31 8:15 ` Conor.Dooley [this message]
2022-08-31 8:15 ` chenguokai17
2022-08-31 8:25 ` Resend for Pure Text: " Xim
2022-08-31 8:34 ` Conor.Dooley
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=999df577-48bd-6ffb-a868-cad8ba4615a1@microchip.com \
--to=conor.dooley@microchip.com \
--cc=aou@eecs.berkeley.edu \
--cc=chenguokai17@mails.ucas.ac.cn \
--cc=liaochang1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
/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).