From: Florian Fainelli <f.fainelli@gmail.com>
To: Stanislav Jakubek <stano.jakubek@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Cc: bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/6] ARM: dts: bcm21664/23550: use CCU compatibles directly
Date: Thu, 8 Jun 2023 15:09:20 -0700 [thread overview]
Message-ID: <5dc1fb31-a025-09e2-1d70-8edc64171a6e@gmail.com> (raw)
In-Reply-To: <65c54bd4076d646623d2a2f518631435522dc628.1685127525.git.stano.jakubek@gmail.com>
On 5/26/23 12:29, Stanislav Jakubek wrote:
> BCM21664 and BCM23550 DTs for some reason use constants from a header file
> for their CCU node compatibles. Change these to use the strings directly.
>
> Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.com>
The reason is to ensure the code and the DTS reference the same string,
applied anyway.
--
Florian
next prev parent reply other threads:[~2023-06-08 22:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 19:28 [PATCH 0/6] ARM: dts: bcm-mobile: DT cleanup Stanislav Jakubek
2023-05-26 19:28 ` [PATCH 1/6] ARM: dts: bcm-mobile: change "" includes to <> where applicable Stanislav Jakubek
2023-06-08 22:07 ` Florian Fainelli
2023-05-26 19:29 ` [PATCH 2/6] ARM: dts: bcm21664/23550: use CCU compatibles directly Stanislav Jakubek
2023-06-08 22:09 ` Florian Fainelli
2023-06-08 22:09 ` Florian Fainelli [this message]
2023-05-26 19:29 ` [PATCH 3/6] ARM: dts: bcm-mobile: move status properties to the end of nodes Stanislav Jakubek
2023-06-08 22:09 ` Florian Fainelli
2023-05-26 19:30 ` [PATCH 4/6] ARM: dts: bcm11351/21664: add UART, I2C node labels Stanislav Jakubek
2023-06-08 22:10 ` Florian Fainelli
2023-05-26 19:30 ` [PATCH 5/6] ARM: dts: bcm21664-garnet: use " Stanislav Jakubek
2023-06-08 22:10 ` Florian Fainelli
2023-05-26 19:30 ` [PATCH 6/6] ARM: dts: bcm28155-ap: " Stanislav Jakubek
2023-05-27 13:37 ` kernel test robot
2023-06-08 22:11 ` Florian Fainelli
2023-06-08 22:31 ` Florian Fainelli
2023-06-18 14:59 ` Stanislav Jakubek
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=5dc1fb31-a025-09e2-1d70-8edc64171a6e@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=stano.jakubek@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;
as well as URLs for NNTP newsgroup(s).