Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yixun Lan <dlan@kernel.org>
To: Andre Heider <a.heider@gmail.com>
Cc: Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	linux-riscv@lists.infradead.org, spacemit@lists.linux.dev
Subject: Re: [PATCH 0/3] riscv: dts: spacemit: add cpu scaling for 3 boards
Date: Fri, 18 Sep 2026 22:54:20 +0000	[thread overview]
Message-ID: <20260918225420-GKB297024@kernel.org> (raw)
In-Reply-To: <ac94820c-5e34-4f07-91de-d08e1d4ef629@gmail.com>

Hi Andre,

On 11:18 Fri 18 Sep     , Andre Heider wrote:
> Hi,
> 
> friendly ping, anything left for me to do here?
> 

Not really, I will handle them shortly, there is one minor
issue, will fix it while applying (no need sending new)..

WARNING: please, no spaces at the start of a line
#33: FILE: arch/riscv/boot/dts/spacemit/k1-orangepi-rv2.dts:87:
+       cpu-supply = <&buck1_0v9>;$


Thanks for the ping (and sorry for the delay)..

-- 
Yixun Lan (dlan)

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

  reply	other threads:[~2026-09-18 22:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 13:32 [PATCH 0/3] riscv: dts: spacemit: add cpu scaling for 3 boards Andre Heider
2026-08-04 13:32 ` [PATCH 1/3] riscv: dts: spacemit: k1-musepi-pro: add cpu scaling Andre Heider
2026-08-04 13:32 ` [PATCH 2/3] riscv: dts: spacemit: orangepi-rv2: Add cpu scaling for K1 SoC Andre Heider
2026-08-04 13:32 ` [PATCH 3/3] riscv: dts: spacemit: orangepi-r2s: " Andre Heider
2026-09-18  9:18 ` [PATCH 0/3] riscv: dts: spacemit: add cpu scaling for 3 boards Andre Heider
2026-09-18 22:54   ` Yixun Lan [this message]
2026-09-19 10:08     ` Andre Heider
2026-09-18 23:40 ` Yixun Lan

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=20260918225420-GKB297024@kernel.org \
    --to=dlan@kernel.org \
    --cc=a.heider@gmail.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=spacemit@lists.linux.dev \
    /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