Re: [PATCH v2 00/11] riscv: kprobes: Clean up instruction simulation
From: Nam Cao
Date: Tue Jul 08 2025 - 06:25:50 EST
On Wed, Jun 04, 2025 at 02:33:06PM +0000, patchwork-bot+linux-riscv@xxxxxxxxxx wrote:
> Hello:
>
> This series was applied to riscv/linux.git (for-next)
> by Alexandre Ghiti <alexghiti@xxxxxxxxxxxx>:
>
> On Wed, 14 May 2025 11:38:39 +0200 you wrote:
> > Hi,
> >
> > There is some instruction-processing code in kprobes simulate code. These
> > code should be insn.h. In fact, most of them is duplicating insn.h.
> >
> > This series remove the duplicated bits and make use of macros already
> > defined in insn.h. The non-duplicated bits are moved into insn.h.
> >
> > [...]
>
> Here is the summary with links:
> - [v2,01/11] riscv: kprobes: Move branch_rs2_idx to insn.h
> https://git.kernel.org/riscv/c/d29656bab74c
> - [v2,02/11] riscv: kprobes: Move branch_funct3 to insn.h
> https://git.kernel.org/riscv/c/da6de46c2eed
> - [v2,03/11] riscv: kprobes: Remove duplication of RV_EXTRACT_JTYPE_IMM
> https://git.kernel.org/riscv/c/6d47d903b18f
> - [v2,04/11] riscv: kprobes: Remove duplication of RV_EXTRACT_RS1_REG
> https://git.kernel.org/riscv/c/5cefc323f32a
> - [v2,05/11] riscv: kprobes: Remove duplication of RV_EXTRACT_BTYPE_IMM
> https://git.kernel.org/riscv/c/a285674909ae
> - [v2,06/11] riscv: kproves: Remove duplication of RVC_EXTRACT_JTYPE_IMM
> https://git.kernel.org/riscv/c/c7196c136e29
> - [v2,07/11] riscv: kprobes: Remove duplication of RVC_EXTRACT_C2_RS1_REG
> https://git.kernel.org/riscv/c/768007ca3fe8
> - [v2,08/11] riscv: kprobes: Remove duplication of RVC_EXTRACT_BTYPE_IMM
> https://git.kernel.org/riscv/c/f2c715fff676
> - [v2,09/11] riscv: kprobes: Remove duplication of RV_EXTRACT_RD_REG
> https://git.kernel.org/riscv/c/284ca2a100de
> - [v2,10/11] riscv: kprobes: Remove duplication of RV_EXTRACT_UTYPE_IMM
> https://git.kernel.org/riscv/c/a60c2933ec74
> - [v2,11/11] riscv: kprobes: Remove duplication of RV_EXTRACT_ITYPE_IMM
> https://git.kernel.org/riscv/c/ee4c45f5cbeb
This series was dropped from 6.16 due to conflict. Can it be re-applied? It
applies cleanly to riscv/for-next.
The same story for:
https://lore.kernel.org/linux-riscv/174904758974.2309006.8809303189389627595.git-patchwork-notify@xxxxxxxxxx/
Best regards,
Nam