From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, aou@eecs.berkeley.edu,
palmer@dabbelt.com, paul.walmsley@sifive.com, l3b2w1@gmail.com,
anil.s.keshavamurthy@intel.com, davem@davemloft.net,
linux-kernel@vger.kernel.org, mhiramat@kernel.org,
naveen.n.rao@linux.ibm.com, conor.dooley@microchip.com
Subject: Re: [PATCH RESEND v9] riscv: add riscv rethook implementation
Date: Sat, 03 Dec 2022 00:40:15 +0000 [thread overview]
Message-ID: <167002801594.8228.14116873241404694670.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221025151831.1097417-1-conor@kernel.org>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 25 Oct 2022 16:18:32 +0100 you wrote:
> From: Binglei Wang <l3b2w1@gmail.com>
>
> Implement the kretprobes on riscv arch by using rethook machenism
> which abstracts general kretprobe info into a struct rethook_node
> to be embedded in the struct kretprobe_instance.
>
> Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> Signed-off-by: Binglei Wang <l3b2w1@gmail.com>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
>
> [...]
Here is the summary with links:
- [RESEND,v9] riscv: add riscv rethook implementation
https://git.kernel.org/riscv/c/b57c2f124098
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-12-03 0:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 15:18 [PATCH RESEND v9] riscv: add riscv rethook implementation Conor Dooley
2022-11-01 13:40 ` binglei wang
2022-11-01 17:07 ` Conor Dooley
2022-12-03 0:32 ` Palmer Dabbelt
2022-12-03 0:40 ` patchwork-bot+linux-riscv [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=167002801594.8228.14116873241404694670.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=davem@davemloft.net \
--cc=l3b2w1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mhiramat@kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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