public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Jamie Iles <jamie@jamieiles.com>
Cc: linux-riscv@lists.infradead.org
Subject: Re: [PATCH v2 0/4] RISC-V: Dynamic ftrace support for RV32I
Date: Fri, 02 Dec 2022 19:00:17 +0000	[thread overview]
Message-ID: <167000761726.13669.7374648603111626230.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221115200832.706370-1-jamie@jamieiles.com>

Hello:

This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Tue, 15 Nov 2022 20:08:28 +0000 you wrote:
> This series enables dynamic ftrace support for RV32I bringing it to
> parity with RV64I.  Most of the work is already there, this is largely
> just assembly fixes to handle register sizes, correct handling of the
> psABI calling convention and Kconfig change.
> 
> Validated with all ftrace boot time self test with qemu for RV32I and
> RV64I in addition to real tracing on an RV32I FPGA design.
> 
> [...]

Here is the summary with links:
  - [v2,1/4] RISC-V: use REG_S/REG_L for mcount
    https://git.kernel.org/riscv/c/8a6841c439df
  - [v2,2/4] RISC-V: reduce mcount save space on RV32
    https://git.kernel.org/riscv/c/3bd7743f8d6d
  - [v2,3/4] RISC-V: preserve a1 in mcount
    https://git.kernel.org/riscv/c/dc58a24db8c1
  - [v2,4/4] RISC-V: enable dynamic ftrace for RV32I
    https://git.kernel.org/riscv/c/f32b4b467ebd

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:[~2022-12-02 19:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 20:08 [PATCH v2 0/4] RISC-V: Dynamic ftrace support for RV32I Jamie Iles
2022-11-15 20:08 ` [PATCH v2 1/4] RISC-V: use REG_S/REG_L for mcount Jamie Iles
2022-11-15 20:08 ` [PATCH v2 2/4] RISC-V: reduce mcount save space on RV32 Jamie Iles
2022-11-16  8:31   ` Andrew Jones
2022-11-15 20:08 ` [PATCH v2 3/4] RISC-V: preserve a1 in mcount Jamie Iles
2022-11-15 20:08 ` [PATCH v2 4/4] RISC-V: enable dynamic ftrace for RV32I Jamie Iles
2022-11-16  8:34 ` [PATCH v2 0/4] RISC-V: Dynamic ftrace support " Andrew Jones
2022-12-02 18:43 ` Palmer Dabbelt
2022-12-02 19:00 ` 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=167000761726.13669.7374648603111626230.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=jamie@jamieiles.com \
    --cc=linux-riscv@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox