From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Udaya Kiran Challa <challauday369@gmail.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
skhan@linuxfoundation.org, me@brighamcampbell.com,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/2] mips: dts: pic32: pic32mzda: Remove unused address-cells, size-cells property
Date: Sat, 26 Sep 2026 11:28:59 +0200 [thread overview]
Message-ID: <areQW4ZAc-rCbEm5@alpha.franken.de> (raw)
In-Reply-To: <20260731174751.86819-1-challauday369@gmail.com>
On Fri, Jul 31, 2026 at 11:17:51PM +0530, Udaya Kiran Challa wrote:
> The #address-cells and #size-cells properties are not strictly
> needed since the child nodes don't have reg properties
>
> Suggested-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Udaya Kiran Challa <challauday369@gmail.com>
> ---
> arch/mips/boot/dts/pic32/pic32mzda.dtsi | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/arch/mips/boot/dts/pic32/pic32mzda.dtsi b/arch/mips/boot/dts/pic32/pic32mzda.dtsi
> index feca35ba56a4..433dff3cf14f 100644
> --- a/arch/mips/boot/dts/pic32/pic32mzda.dtsi
> +++ b/arch/mips/boot/dts/pic32/pic32mzda.dtsi
> @@ -76,8 +76,6 @@ evic: interrupt-controller@1f810000 {
> };
>
> pic32_pinctrl: pinctrl@1f801400 {
> - #address-cells = <1>;
> - #size-cells = <1>;
> compatible = "microchip,pic32mzda-pinctrl";
> reg = <0x1f801400 0x400>;
> clocks = <&rootclk PB1CLK>;
> --
> 2.34.1
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:[~2026-09-26 10:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 17:47 [PATCH v5 2/2] mips: dts: pic32: pic32mzda: Remove unused address-cells, size-cells property Udaya Kiran Challa
2026-09-26 9:28 ` 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=areQW4ZAc-rCbEm5@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=challauday369@gmail.com \
--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=me@brighamcampbell.com \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.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.