All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emil Renner Berthing <emil.renner.berthing@canonical.com>
To: Jisheng Zhang <jszhang@kernel.org>,
	Conor Dooley <conor@kernel.org>,
	 Rob Herring <robh+dt@kernel.org>,
	 Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	 Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 Albert Ou <aou@eecs.berkeley.edu>,
	Emil Renner Berthing <kernel@esmil.dk>
Cc: linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
	 linux-kernel@vger.kernel.org,
	 Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v3 4/6] riscv: dts: starfive: visionfive 2: use cpus label for timebase freq
Date: Fri, 19 Apr 2024 15:05:40 -0700	[thread overview]
Message-ID: <CAJM55Z96TnvHNwN5JPKLYywO7eiRh54dJSaFD6Avsy3nmM0bjA@mail.gmail.com> (raw)
In-Reply-To: <20240131132600.4067-5-jszhang@kernel.org>

Jisheng Zhang wrote:
> As pointed out by Krzysztof "Board should not bring new CPU nodes.
> Override by label instead."
>
> Suggested-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: Jisheng Zhang <jszhang@kernel.org>

Reviewed-by: Emil Renner Berthing <emil.renner.berthing@canonical.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: Emil Renner Berthing <emil.renner.berthing@canonical.com>
To: Jisheng Zhang <jszhang@kernel.org>,
	Conor Dooley <conor@kernel.org>,
	 Rob Herring <robh+dt@kernel.org>,
	 Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	 Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 Albert Ou <aou@eecs.berkeley.edu>,
	Emil Renner Berthing <kernel@esmil.dk>
Cc: linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
	 linux-kernel@vger.kernel.org,
	 Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v3 4/6] riscv: dts: starfive: visionfive 2: use cpus label for timebase freq
Date: Fri, 19 Apr 2024 15:05:40 -0700	[thread overview]
Message-ID: <CAJM55Z96TnvHNwN5JPKLYywO7eiRh54dJSaFD6Avsy3nmM0bjA@mail.gmail.com> (raw)
In-Reply-To: <20240131132600.4067-5-jszhang@kernel.org>

Jisheng Zhang wrote:
> As pointed out by Krzysztof "Board should not bring new CPU nodes.
> Override by label instead."
>
> Suggested-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: Jisheng Zhang <jszhang@kernel.org>

Reviewed-by: Emil Renner Berthing <emil.renner.berthing@canonical.com>

  reply	other threads:[~2024-04-19 22:05 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 13:25 [PATCH v3 0/6] riscv: dts: starfive: add Milkv Mars board device tree Jisheng Zhang
2024-01-31 13:25 ` Jisheng Zhang
2024-01-31 13:25 ` [PATCH v3 1/6] riscv: dts: starfive: add 'cpus' label to jh7110 and jh7100 soc dtsi Jisheng Zhang
2024-01-31 13:25   ` Jisheng Zhang
2024-04-19 22:04   ` Emil Renner Berthing
2024-04-19 22:04     ` Emil Renner Berthing
2024-01-31 13:25 ` [PATCH v3 2/6] dt-bindings: riscv: starfive: add Milkv Mars board Jisheng Zhang
2024-01-31 13:25   ` Jisheng Zhang
2024-04-19 22:04   ` Emil Renner Berthing
2024-04-19 22:04     ` Emil Renner Berthing
2024-01-31 13:25 ` [PATCH v3 3/6] riscv: dts: starfive: visionfive 2: update sound and codec dt node name Jisheng Zhang
2024-01-31 13:25   ` Jisheng Zhang
2024-04-19 22:05   ` Emil Renner Berthing
2024-04-19 22:05     ` Emil Renner Berthing
2024-01-31 13:25 ` [PATCH v3 4/6] riscv: dts: starfive: visionfive 2: use cpus label for timebase freq Jisheng Zhang
2024-01-31 13:25   ` Jisheng Zhang
2024-04-19 22:05   ` Emil Renner Berthing [this message]
2024-04-19 22:05     ` Emil Renner Berthing
2024-01-31 13:25 ` [PATCH v3 5/6] riscv: dts: starfive: introduce a common board dtsi for jh7110 based boards Jisheng Zhang
2024-01-31 13:25   ` Jisheng Zhang
2024-01-31 13:26 ` [PATCH v3 6/6] riscv: dts: starfive: add Milkv Mars board device tree Jisheng Zhang
2024-01-31 13:26   ` Jisheng Zhang
2024-02-06 19:13   ` Conor Dooley
2024-02-06 19:13     ` Conor Dooley
2024-03-27 18:06     ` Conor Dooley
2024-03-27 18:06       ` Conor Dooley
2024-03-28 10:08       ` Jisheng Zhang
2024-03-28 10:08         ` Jisheng Zhang
2024-03-28 12:45         ` Emil Renner Berthing
2024-03-28 12:45           ` Emil Renner Berthing
2024-03-29  2:32           ` Jisheng Zhang
2024-03-29  2:32             ` Jisheng Zhang
2024-03-28 21:28     ` Heinrich Schuchardt
2024-03-28 21:28       ` Heinrich Schuchardt
2024-03-29  2:31       ` Jisheng Zhang
2024-03-29  2:31         ` Jisheng Zhang
2024-04-01 13:28         ` Heinrich Schuchardt
2024-04-01 13:28           ` Heinrich Schuchardt
2024-04-01 14:44           ` Jisheng Zhang
2024-04-01 14:44             ` Jisheng Zhang
2024-04-19 22:11             ` Emil Renner Berthing
2024-04-19 22:11               ` Emil Renner Berthing

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=CAJM55Z96TnvHNwN5JPKLYywO7eiRh54dJSaFD6Avsy3nmM0bjA@mail.gmail.com \
    --to=emil.renner.berthing@canonical.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jszhang@kernel.org \
    --cc=kernel@esmil.dk \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@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 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.