public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: Paul Walmsley <pjw@kernel.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	 Michael Turquette <mturquette@baylibre.com>,
	 Stephen Boyd <sboyd@kernel.org>,
	Rahul Pathak <rpathak@ventanamicro.com>,
	 Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	 Anup Patel <apatel@ventanamicro.com>,
	linux-clk@vger.kernel.org,  linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: COMMON_CLK_RPMI should depend on RISCV
Date: Wed, 1 Oct 2025 19:31:00 -0600 (MDT)	[thread overview]
Message-ID: <82323d78-0111-aa0d-cafb-d0c04071c6ea@kernel.org> (raw)
In-Reply-To: <6555b47f-919b-b56c-4a76-352c904343c2@kernel.org>

On Wed, 1 Oct 2025, Paul Walmsley wrote:

> On Tue, 30 Sep 2025, Geert Uytterhoeven wrote:
> 
> > And perhaps the "default RISCV" should be dropped, too?
> 
> Probably.  I guess we should just add this to the arch/riscv defconfig 
> instead.  Let's wait on this one for a few days to see if anyone has any 
> comments, and consider that change for v6.18-rc fixes.

Sorry, this one got garbled on the way out.  I meant to say that we should 
think about whether it makes sense to use a more fine-grained way to 
enable this by default.


- Paul

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

  reply	other threads:[~2025-10-02  1:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30 14:50 [PATCH] clk: COMMON_CLK_RPMI should depend on RISCV Geert Uytterhoeven
2025-10-02  1:15 ` Paul Walmsley
2025-10-02  1:31   ` Paul Walmsley [this message]
2025-10-02  9:36   ` Conor Dooley
2025-10-02 14:34     ` Anup Patel

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=82323d78-0111-aa0d-cafb-d0c04071c6ea@kernel.org \
    --to=pjw@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=apatel@ventanamicro.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mturquette@baylibre.com \
    --cc=rpathak@ventanamicro.com \
    --cc=sboyd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox