From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
"Arınç ÜNAL" <arinc.unal@arinc9.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Rob Herring" <robh+dt@kernel.org>,
"Scott Branden" <scott.branden@broadcom.com>,
"Christian Lamparter" <chunkeey@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 3/4] ARM: dts: BCM5301X: Fix compatible strings for BCM53012 and BCM53016 SoC
Date: Mon, 4 Apr 2022 11:38:16 -0700 [thread overview]
Message-ID: <20220404183816.2317832-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20220402204622.3360-3-arinc.unal@arinc9.com>
On Sat, 2 Apr 2022 23:46:21 +0300, Arınç ÜNAL <arinc.unal@arinc9.com> wrote:
> Fix compatible strings for devicetrees using the BCM53012 and BCM53016 SoC.
>
> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
> ---
Applied to https://github.com/Broadcom/stblinux/commits/devicetree/next, thanks!
--
Florian
next prev parent reply other threads:[~2022-04-04 21:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 20:46 [PATCH v2 1/4] dt-bindings: arm: bcm: fix BCM53012 and BCM53016 SoC strings Arınç ÜNAL
2022-04-02 20:46 ` [PATCH v2 2/4] dt-bindings: arm: bcm: create new description for BCM53016 Arınç ÜNAL
2022-04-04 18:38 ` Florian Fainelli
2022-04-02 20:46 ` [PATCH v2 3/4] ARM: dts: BCM5301X: Fix compatible strings for BCM53012 and BCM53016 SoC Arınç ÜNAL
2022-04-03 7:53 ` Krzysztof Kozlowski
2022-04-04 18:38 ` Florian Fainelli [this message]
2022-04-02 20:46 ` [PATCH v2 4/4] dt-bindings: arm: bcm: add bindings for Asus RT-AC88U Arınç ÜNAL
2022-04-04 18:38 ` Florian Fainelli
2022-04-03 7:53 ` [PATCH v2 1/4] dt-bindings: arm: bcm: fix BCM53012 and BCM53016 SoC strings Krzysztof Kozlowski
2022-04-04 18:37 ` 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=20220404183816.2317832-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arinc.unal@arinc9.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=chunkeey@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=scott.branden@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).