From: Miquel Raynal <miquel.raynal@bootlin.com>
To: William Zhang <william.zhang@broadcom.com>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
Hauke Mehrtens <hauke@hauke-m.de>,
zajec5@gmail.com, bcm-kernel-feedback-list@broadcom.com,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH -next] ARM: dts: BCM5301X: Drop extra NAND controller compatible
Date: Wed, 04 Feb 2026 21:36:01 +0100 [thread overview]
Message-ID: <87ldh8fdqm.fsf@bootlin.com> (raw)
In-Reply-To: <CAHi4H7EVLsgVL5KCERTX5XBNTMvZDNxePzo48Zp5dsfDdoCV1Q@mail.gmail.com> (William Zhang's message of "Wed, 4 Feb 2026 09:36:51 -0800")
Hello William,
>> diff --git a/arch/arm/boot/dts/broadcom/bcm-ns.dtsi b/arch/arm/boot/dts/broadcom/bcm-ns.dtsi
>> index d0d5f7e52a91..46b650abdb90 100644
>> --- a/arch/arm/boot/dts/broadcom/bcm-ns.dtsi
>> +++ b/arch/arm/boot/dts/broadcom/bcm-ns.dtsi
>> @@ -479,7 +479,7 @@ thermal: thermal@2c0 {
>> };
>>
>> nand_controller: nand-controller@18028000 {
>> - compatible = "brcm,nand-iproc", "brcm,brcmnand-v6.1", "brcm,brcmnand";
>> + compatible = "brcm,nand-iproc", "brcm,brcmnand-v6.1";
>> reg = <0x18028000 0x600>, <0x1811a408 0x600>, <0x18028f00 0x20>;
>> reg-names = "nand", "iproc-idm", "iproc-ext";
>> interrupts = <GIC_SPI 68 IRQ_TYPE_LEVEL_HIGH>;
>
> Acked-by: William Zhang <william.zhang@broadcom.com>
Do you mind if I take it on top of the commit it fixes?
Thanks,
Miquèl
next prev parent reply other threads:[~2026-02-04 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 9:15 [PATCH -next] ARM: dts: BCM5301X: Drop extra NAND controller compatible Miquel Raynal
2026-02-04 16:00 ` Rob Herring
2026-02-04 17:36 ` William Zhang
2026-02-04 20:36 ` Miquel Raynal [this message]
2026-02-04 21:21 ` Florian Fainelli
2026-02-05 8:49 ` Miquel Raynal
2026-02-04 21:56 ` William Zhang
2026-02-04 18:26 ` Florian Fainelli
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=87ldh8fdqm.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=hauke@hauke-m.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=william.zhang@broadcom.com \
--cc=zajec5@gmail.com \
/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.