Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Changhuang Liang <changhuang.liang@starfivetech.com>
Cc: Emil Renner Berthing <kernel@esmil.dk>,
	Joel Stanley <jms@oss.tenstorrent.com>,
	Drew Fustini <dfustini@oss.tenstorrent.com>,
	Darshan Prajapati <darshan.prajapati@einfochips.com>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>, Rob Herring <robh@kernel.org>,
	Alexandre Ghiti <alex@ghiti.fr>, Anup Patel <anup@brainfault.org>,
	Hal Feng <hal.feng@starfivetech.com>,
	Guodong Xu <guodong@riscstar.com>, Yixun Lan <dlan@kernel.org>,
	Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Albert Ou <aou@eecs.berkeley.edu>, E Shattow <e@freeshell.de>,
	Ley Foon Tan <leyfoon.tan@starfivetech.com>,
	Junhui Liu <junhui.liu@pigmoral.tech>,
	Daniel Lezcano <daniel.lezcano@kernel.org>,
	Michal Simek <michal.simek@amd.com>,
	Paul Walmsley <pjw@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Samuel Holland <samuel.holland@sifive.com>,
	Michael Zhu <michael.zhu@starfivetech.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Thomas Gleixner <tglx@kernel.org>,
	Ji Sheng Teoh <jisheng.teoh@starfivetech.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH v2 4/4] riscv: dts: starfive: jhb100: Add JHB100 base DT
Date: Thu, 7 May 2026 18:09:58 +0100	[thread overview]
Message-ID: <20260507-marina-cost-dc8e597ccf26@spud> (raw)
In-Reply-To: <NT0PR01MB1216090A629C0095441617F6F23C2@NT0PR01MB1216.CHNPR01.prod.partner.outlook.cn>


[-- Attachment #1.1: Type: text/plain, Size: 469 bytes --]

On Thu, May 07, 2026 at 09:05:44AM +0000, Changhuang Liang wrote:
> > On Wed, May 06, 2026 at 01:59:37AM -0700, Changhuang Liang wrote:
> > 
> > > +	clk_uart: clock-25000000 {
> > > +		compatible = "fixed-clock"; /* Initial clock handler for UART */
> > 
> > What does this comment mean?
> 
> Here it's just a temporary clock; it will be replaced by the clock driver later.


In that case, it is highly unlikely that I merge this without the clock
driver.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

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

      reply	other threads:[~2026-05-07 17:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06  8:59 [PATCH v2 0/4] Initial device tree support for StarFive JHB100 SoC Changhuang Liang
2026-05-06  8:59 ` [PATCH v2 1/4] dt-bindings: riscv: Add StarFive Dubhe-70 compatibles Changhuang Liang
2026-05-07  6:00   ` Hal Feng
2026-05-06  8:59 ` [PATCH v2 2/4] dt-bindings: interrupt-controller: Add StarFive JHB100 plic Changhuang Liang
2026-05-07  6:09   ` Hal Feng
2026-05-06  8:59 ` [PATCH v2 3/4] dt-bindings: riscv: Add StarFive JHB100 SoC Changhuang Liang
2026-05-07  6:21   ` Hal Feng
2026-05-06  8:59 ` [PATCH v2 4/4] riscv: dts: starfive: jhb100: Add JHB100 base DT Changhuang Liang
2026-05-06 17:44   ` Conor Dooley
2026-05-07  9:05     ` Changhuang Liang
2026-05-07 17:09       ` Conor Dooley [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=20260507-marina-cost-dc8e597ccf26@spud \
    --to=conor@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=changhuang.liang@starfivetech.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel.lezcano@kernel.org \
    --cc=darshan.prajapati@einfochips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dfustini@oss.tenstorrent.com \
    --cc=dlan@kernel.org \
    --cc=e@freeshell.de \
    --cc=guodong@riscstar.com \
    --cc=hal.feng@starfivetech.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=jisheng.teoh@starfivetech.com \
    --cc=jms@oss.tenstorrent.com \
    --cc=junhui.liu@pigmoral.tech \
    --cc=kernel@esmil.dk \
    --cc=krzk+dt@kernel.org \
    --cc=leyfoon.tan@starfivetech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=michael.zhu@starfivetech.com \
    --cc=michal.simek@amd.com \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=robh@kernel.org \
    --cc=samuel.holland@sifive.com \
    --cc=tglx@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