From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
Matthew Hagan <mnhagan88@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Rob Herring <robh+dt@kernel.org>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/5] ARM: dts: NSP: Add bcm958623hr board name to dts
Date: Thu, 2 Sep 2021 14:04:54 -0700 [thread overview]
Message-ID: <20210902210454.3102738-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20210829223752.2748091-1-mnhagan88@gmail.com>
On Sun, 29 Aug 2021 22:37:47 +0000, Matthew Hagan <mnhagan88@gmail.com> wrote:
> This board was previously added to
> Documentation/devicetree/bindings/arm/bcm/brcm,nsp.yaml
> however the dts file was not updated to reflect this change. This patch
> corrects bcm958623hr.dts by adding the board name to the compatible.
>
> Signed-off-by: Matthew Hagan <mnhagan88@gmail.com>
> ---
Applied to https://github.com/Broadcom/stblinux/commits/devicetree/next, thanks!
--
Florian
prev parent reply other threads:[~2021-09-02 21:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 22:37 [PATCH v2 1/5] ARM: dts: NSP: Add bcm958623hr board name to dts Matthew Hagan
2021-08-29 22:37 ` [PATCH v2 2/5] ARM: dts: NSP: Fix mpcore, mmc node names Matthew Hagan
2021-09-02 21:05 ` Florian Fainelli
2021-08-29 22:37 ` [PATCH v2 3/5] ARM: dts: NSP: Fix MDIO mux " Matthew Hagan
2021-08-30 0:27 ` Andrew Lunn
2021-09-02 21:05 ` Florian Fainelli
2021-08-29 22:37 ` [PATCH v2 4/5] ARM: dts: NSP: Fix MX64/MX65 eeprom node name Matthew Hagan
2021-09-02 21:05 ` Florian Fainelli
2021-08-29 22:37 ` [PATCH v2 5/5] ARM: dts: NSP: Fix MX65 MDIO mux warnings Matthew Hagan
2021-09-02 21:06 ` Florian Fainelli
2021-09-02 21:04 ` 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=20210902210454.3102738-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mnhagan88@gmail.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.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;
as well as URLs for NNTP newsgroup(s).