From: Florian Fainelli <florian.fainelli@broadcom.com>
To: bcm-kernel-feedback-list@broadcom.com,
Miquel Raynal <miquel.raynal@bootlin.com>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Hauke Mehrtens <hauke@hauke-m.de>,
zajec5@gmail.com
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
William Zhang <william.zhang@broadcom.com>,
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, 4 Feb 2026 10:26:17 -0800 [thread overview]
Message-ID: <20260204182617.1154751-1-florian.fainelli@broadcom.com> (raw)
In-Reply-To: <20260204091530.624230-1-miquel.raynal@bootlin.com>
From: Florian Fainelli <f.fainelli@gmail.com>
On Wed, 4 Feb 2026 10:15:30 +0100, Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> Fix the dtbs_check warning introduced when the brcm,brcmnand fallback
> compatible got removed for iProc machines.
>
> Fixes: 4db35366d6dc ("dt-bindings: mtd: brcm,brcmnand: Drop "brcm,brcmnand" compatible for iProc")
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> ---
Applied to https://github.com/Broadcom/stblinux/commits/devicetree/next, thanks!
--
Florian
prev parent reply other threads:[~2026-02-04 18:26 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
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 [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=20260204182617.1154751-1-florian.fainelli@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox