mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: Vivian Wang <wangruikang@iscas.ac.cn>
Cc: Paul Walmsley <pjw@kernel.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	 "linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	 "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	 duchangbin <changbin.du@huawei.com>,
	Alexandre Ghiti <alex@ghiti.fr>,
	 andybnac@gmail.com
Subject: Re: [PATCH] riscv: Prevent early kernel panic in instrumented apply_early_boot_alternatives
Date: Thu, 9 Oct 2025 17:33:11 -0600 (MDT)	[thread overview]
Message-ID: <58b5a08f-b10c-668b-fbb7-cf44ef2ac940@kernel.org> (raw)
In-Reply-To: <4de90ac7-f05d-4c16-a5c5-8101f5d2fe91@iscas.ac.cn>

[-- Attachment #1: Type: text/plain, Size: 560 bytes --]

Hi Vivian,

On Thu, 9 Oct 2025, Vivian Wang wrote:
> On 10/9/25 10:01, Paul Walmsley wrote:
> > On Wed, 25 Jun 2025, duchangbin wrote:
> >
> > [...]
> >
> > Working on cleaning out Patchwork.  Was there any further conclusion 
> > reached on this patch, or more broadly, static ftrace ?
> 
> Static ftrace for riscv is no longer supported in 6.17. config RISCV is now:
> 
>     select DYNAMIC_FTRACE if FUNCTION_TRACER
> 
> Since commit 5874ca4c6280 ("riscv: Stop supporting static ftrace"). This
> patch should be obsolete.

Thanks for the followup.

- Paul

      reply	other threads:[~2025-10-09 23:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 11:30 Changbin Du
2025-06-24 12:54 ` Alexandre Ghiti
2025-06-25  3:10   ` duchangbin
2025-10-09  2:01     ` Paul Walmsley
2025-10-09  6:31       ` Vivian Wang
2025-10-09 23:33         ` Paul Walmsley [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=58b5a08f-b10c-668b-fbb7-cf44ef2ac940@kernel.org \
    --to=pjw@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=andybnac@gmail.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=changbin.du@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=wangruikang@iscas.ac.cn \
    /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
all inboxes | Powered by JetHome®