From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Aleksander Jan Bajkowski <olek2@wp.pl>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mips: lantiq: danube: add missing properties to cpu node
Date: Fri, 29 Aug 2025 12:23:24 +0200 [thread overview]
Message-ID: <aLF_nDfoiQ76Yqrj@alpha.franken.de> (raw)
In-Reply-To: <20250811115818.735670-1-olek2@wp.pl>
On Mon, Aug 11, 2025 at 01:58:15PM +0200, Aleksander Jan Bajkowski wrote:
> This fixes the following warnings:
> arch/mips/boot/dts/lantiq/danube_easy50712.dtb: cpus: '#address-cells' is a required property
> from schema $id: http://devicetree.org/schemas/cpus.yaml#
> arch/mips/boot/dts/lantiq/danube_easy50712.dtb: cpus: '#size-cells' is a required property
> from schema $id: http://devicetree.org/schemas/cpus.yaml#
> arch/mips/boot/dts/lantiq/danube_easy50712.dtb: cpu@0 (mips,mips24Kc): 'reg' is a required property
> from schema $id: http://devicetree.org/schemas/mips/cpus.yaml#
>
> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
> ---
> arch/mips/boot/dts/lantiq/danube.dtsi | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/mips/boot/dts/lantiq/danube.dtsi b/arch/mips/boot/dts/lantiq/danube.dtsi
> index 7a7ba66aa534..0a942bc09143 100644
> --- a/arch/mips/boot/dts/lantiq/danube.dtsi
> +++ b/arch/mips/boot/dts/lantiq/danube.dtsi
> @@ -5,8 +5,12 @@ / {
> compatible = "lantiq,xway", "lantiq,danube";
>
> cpus {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> cpu@0 {
> compatible = "mips,mips24Kc";
> + reg = <0>;
> };
> };
>
> --
> 2.47.2
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2025-08-29 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 11:58 Aleksander Jan Bajkowski
2025-08-29 10:23 ` Thomas Bogendoerfer [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=aLF_nDfoiQ76Yqrj@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=olek2@wp.pl \
--cc=robh@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
all inboxes | Powered by JetHome®