All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, jszhang@kernel.org,
	bjorn@kernel.org, pulehui@huawei.com, daniel@iogearbox.net,
	puranjay12@gmail.com, zong.li@sifive.com, mhiramat@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] ftrace fixes
Date: Thu, 04 Apr 2024 22:20:32 +0000	[thread overview]
Message-ID: <171226923209.6067.4357956363525619450.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240326203017.310422-1-alexghiti@rivosinc.com>

Hello:

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

On Tue, 26 Mar 2024 21:30:15 +0100 you wrote:
> Both were reported recently as there are efforts ongoing to
> reimplement ftrace on riscv and both are independent of this rework,
> so here they are.
> 
> Alexandre Ghiti (2):
>   riscv: Fix warning by declaring arch_cpu_idle() as noinstr
>   riscv: Disable preemption when using patch_map()
> 
> [...]

Here is the summary with links:
  - [1/2] riscv: Fix warning by declaring arch_cpu_idle() as noinstr
    https://git.kernel.org/riscv/c/8a48ea87ce89
  - [2/2] riscv: Disable preemption when using patch_map()
    https://git.kernel.org/riscv/c/a370c2419e46

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: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, jszhang@kernel.org,
	bjorn@kernel.org, pulehui@huawei.com, daniel@iogearbox.net,
	puranjay12@gmail.com, zong.li@sifive.com, mhiramat@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] ftrace fixes
Date: Thu, 04 Apr 2024 22:20:32 +0000	[thread overview]
Message-ID: <171226923209.6067.4357956363525619450.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240326203017.310422-1-alexghiti@rivosinc.com>

Hello:

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

On Tue, 26 Mar 2024 21:30:15 +0100 you wrote:
> Both were reported recently as there are efforts ongoing to
> reimplement ftrace on riscv and both are independent of this rework,
> so here they are.
> 
> Alexandre Ghiti (2):
>   riscv: Fix warning by declaring arch_cpu_idle() as noinstr
>   riscv: Disable preemption when using patch_map()
> 
> [...]

Here is the summary with links:
  - [1/2] riscv: Fix warning by declaring arch_cpu_idle() as noinstr
    https://git.kernel.org/riscv/c/8a48ea87ce89
  - [2/2] riscv: Disable preemption when using patch_map()
    https://git.kernel.org/riscv/c/a370c2419e46

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:[~2024-04-04 22:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26 20:30 [PATCH 0/2] ftrace fixes Alexandre Ghiti
2024-03-26 20:30 ` Alexandre Ghiti
2024-03-26 20:30 ` [PATCH 1/2] riscv: Fix warning by declaring arch_cpu_idle() as noinstr Alexandre Ghiti
2024-03-26 20:30   ` Alexandre Ghiti
2024-03-27 14:23   ` Andy Chiu
2024-03-27 14:23     ` Andy Chiu
2024-03-26 20:30 ` [PATCH 2/2] riscv: Disable preemption when using patch_map() Alexandre Ghiti
2024-03-26 20:30   ` Alexandre Ghiti
2024-03-26 22:30 ` [PATCH 0/2] ftrace fixes Puranjay Mohan
2024-03-26 22:30   ` Puranjay Mohan
2024-04-04 22:20 ` patchwork-bot+linux-riscv [this message]
2024-04-04 22:20   ` patchwork-bot+linux-riscv
  -- strict thread matches above, loose matches on Subject: below --
2017-11-01 14:33 [PATCH 0/2] Ftrace fixes Julien Thierry

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=171226923209.6067.4357956363525619450.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alexghiti@rivosinc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=bjorn@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jszhang@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mhiramat@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=pulehui@huawei.com \
    --cc=puranjay12@gmail.com \
    --cc=zong.li@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 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.