From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Florian Fainelli <f.fainelli@gmail.com>, linux-kernel@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/3] dt-bindings: arm: bcm: Refer to the YAML binding for MEMC
Date: Fri, 22 Jul 2022 21:19:55 +0200 [thread overview]
Message-ID: <0974ebc0-8426-c889-b16a-1d35a4e4309e@linaro.org> (raw)
In-Reply-To: <20220722184138.2666241-3-f.fainelli@gmail.com>
On 22/07/2022 20:41, Florian Fainelli wrote:
> Remove the list of existing compatible strings and prefer to use the
> YAML binding which more complete and up to date.
Ah, so this is partial conversion from TXT? Then please squash it with
previous commit and extend the commit msg.
>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
> .../devicetree/bindings/arm/bcm/brcm,brcmstb.txt | 11 ++---------
> 1 file changed, 2 insertions(+), 9 deletions(-)
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-07-22 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 18:41 [PATCH 0/3] Add Broadcom STB memory controller driver Florian Fainelli
2022-07-22 18:41 ` [PATCH 1/3] dt-bindings: memory-controller: Document Broadcom STB MEMC Florian Fainelli
2022-07-22 19:18 ` Krzysztof Kozlowski
2022-07-22 18:41 ` [PATCH 2/3] dt-bindings: arm: bcm: Refer to the YAML binding for MEMC Florian Fainelli
2022-07-22 19:19 ` Krzysztof Kozlowski [this message]
2022-07-22 18:41 ` [PATCH 3/3] memory: Add Broadcom STB memory controller driver Florian Fainelli
2022-07-22 19:31 ` Krzysztof Kozlowski
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=0974ebc0-8426-c889-b16a-1d35a4e4309e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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).