From: Jae Hyun Yoo <quic_jaehyoo@quicinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Joel Stanley <joel@jms.id.au>, "Andrew Jeffery" <andrew@aj.id.au>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: arm: aspeed: adjust qcom,dc-scm-v1-bmc compatible after rename
Date: Thu, 4 Aug 2022 08:14:28 -0700 [thread overview]
Message-ID: <7f698b2b-bc4f-e5a4-fdf1-2de228791607@quicinc.com> (raw)
In-Reply-To: <20220804150935.121890-1-krzysztof.kozlowski@linaro.org>
Hi Krzysztof,
On 8/4/2022 8:09 AM, Krzysztof Kozlowski wrote:
> The Nuvia DC-SCM BMC board compatible was renamed iin commit
> 7f058112873e ("ARM: dts: aspeed: nuvia: rename vendor nuvia to qcom"),
> so adjust the bindings as well.
>
> Fixes: f77024c80147 ("dt-bindings: arm: aspeed: document board compatibles")
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> ---
Acked-by: Jae Hyun Yoo <quic_jaehyoo@quicinc.com>
Thanks,
Jae
>
> Changes since v1:
> 1. Use proper qcom compatible.
> ---
> Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml b/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
> index 1895ce9de461..4f0b308e9f0f 100644
> --- a/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
> +++ b/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
> @@ -80,7 +80,7 @@ properties:
> - ibm,tacoma-bmc
> - inventec,transformer-bmc
> - jabil,rbp-bmc
> - - nuvia,dc-scm-bmc
> + - qcom,dc-scm-v1-bmc
> - quanta,s6q-bmc
> - const: aspeed,ast2600
>
next prev parent reply other threads:[~2022-08-04 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 15:09 Krzysztof Kozlowski
2022-08-04 15:14 ` Jae Hyun Yoo [this message]
2022-08-09 18:37 ` Rob Herring
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=7f698b2b-bc4f-e5a4-fdf1-2de228791607@quicinc.com \
--to=quic_jaehyoo@quicinc.com \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.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
all inboxes | Powered by JetHome®