From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"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,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH 1/2] dt-bindings: arm: bcm: fix BCM53012 and BCM53016 SoC strings
Date: Sat, 2 Apr 2022 23:41:18 +0300 [thread overview]
Message-ID: <bf363c60-3432-7b98-97c5-0dbeddad8a4d@arinc9.com> (raw)
In-Reply-To: <fbbd44cc-e839-9532-962a-538ce834930c@linaro.org>
On 02/04/2022 19:28, Krzysztof Kozlowski wrote:
> On 01/04/2022 19:24, Arınç ÜNAL wrote:
>> Fix inaccurate SoC strings brcm,brcm53012 and brcm,brcm53016 to respectively
>> brcm,bcm53012 and brcm,bcm53016.
>>
>> Create a new description for BCM53016 and move Meraki MR32 under it.
>>
>> Fixes: 4cb5201fcb5d ("dt-bindings: arm: bcm: Convert BCM4708 to YAML")
>> Fixes: a2e385f5374d ("dt-bindings: ARM: add bindings for the Meraki MR32")
>> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
>> ---
>> brcm,bcm53012 string was silently changed to brcm,brcm53012 after
>> converting to YAML. Let me know if this was intentional.
>>
>
> Thanks for your patch. This looks like 2 or 3 separate patches:
> 1. Correct meraki and BCM53016 bindings,
> 2. Rename brcm->bcm, in bindings,
> 3. Change DTS.
Will send v2, thanks.
Arınç
prev parent reply other threads:[~2022-04-02 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 17:24 Arınç ÜNAL
2022-04-01 17:24 ` [PATCH 2/2] dt-bindings: arm: bcm: add bindings for Asus RT-AC88U Arınç ÜNAL
2022-04-02 16:28 ` Krzysztof Kozlowski
2022-04-02 16:28 ` [PATCH 1/2] dt-bindings: arm: bcm: fix BCM53012 and BCM53016 SoC strings Krzysztof Kozlowski
2022-04-02 20:41 ` Arınç ÜNAL [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=bf363c60-3432-7b98-97c5-0dbeddad8a4d@arinc9.com \
--to=arinc.unal@arinc9.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=chunkeey@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--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
all inboxes | Powered by JetHome®