All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Nam Cao <namcao@linutronix.de>
Cc: linux-riscv@lists.infradead.org, pjw@kernel.org,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: kprobes: Add test case for c.jal instruction simulation
Date: Fri, 10 Jul 2026 18:40:12 +0000	[thread overview]
Message-ID: <178370881238.810467.12745723809097187662.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260627115051.3235783-1-namcao@linutronix.de>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.org>:

On Sat, 27 Jun 2026 13:50:51 +0200 you wrote:
> Add test validating that kprobes correctly simulate the c.jal
> instruction.
> 
> Signed-off-by: Nam Cao <namcao@linutronix.de>
> ---
> the test fails without c.jal simulation patch:
> https://lore.kernel.org/linux-riscv/20260627001939.3847-1-xiaofengmian@163.com/
> 
> [...]

Here is the summary with links:
  - riscv: kprobes: Add test case for c.jal instruction simulation
    https://git.kernel.org/riscv/c/0161aa173c38

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Nam Cao <namcao@linutronix.de>
Cc: linux-riscv@lists.infradead.org, pjw@kernel.org,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: kprobes: Add test case for c.jal instruction simulation
Date: Fri, 10 Jul 2026 18:40:12 +0000	[thread overview]
Message-ID: <178370881238.810467.12745723809097187662.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260627115051.3235783-1-namcao@linutronix.de>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.org>:

On Sat, 27 Jun 2026 13:50:51 +0200 you wrote:
> Add test validating that kprobes correctly simulate the c.jal
> instruction.
> 
> Signed-off-by: Nam Cao <namcao@linutronix.de>
> ---
> the test fails without c.jal simulation patch:
> https://lore.kernel.org/linux-riscv/20260627001939.3847-1-xiaofengmian@163.com/
> 
> [...]

Here is the summary with links:
  - riscv: kprobes: Add test case for c.jal instruction simulation
    https://git.kernel.org/riscv/c/0161aa173c38

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2026-07-10 18:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-27 11:50 [PATCH] riscv: kprobes: Add test case for c.jal instruction simulation Nam Cao
2026-06-27 11:50 ` Nam Cao
2026-06-27 12:58 ` Xiaofeng Yuan
2026-06-27 13:25   ` Nam Cao
2026-07-01 10:46 ` Xiaofeng Yuan
2026-07-01 10:46   ` Xiaofeng Yuan
2026-07-10 18:40 ` patchwork-bot+linux-riscv [this message]
2026-07-10 18:40   ` patchwork-bot+linux-riscv

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=178370881238.810467.12745723809097187662.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=namcao@linutronix.de \
    --cc=palmer@dabbelt.com \
    --cc=pjw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.