From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Joel Stanley" <joel@jms.id.au>,
linux-aspeed@lists.ozlabs.org
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Jae Hyun Yoo" <quic_jaehyoo@quicinc.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
"Rob Herring" <robh@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] dt-bindings: arm: aspeed: adjust qcom,dc-scm-v1-bmc compatible after rename
Date: Fri, 23 Sep 2022 09:31:35 +0930 [thread overview]
Message-ID: <c5acf780-7a9d-442c-a41c-efc69e5d0ed3@app.fastmail.com> (raw)
In-Reply-To: <1c33bf6d-b458-b2bb-3116-ed20b9cadc0e@linaro.org>
On Thu, 22 Sep 2022, at 16:19, Krzysztof Kozlowski wrote:
> On 11/08/2022 08:29, Krzysztof Kozlowski wrote:
>> The Nuvia DC-SCM BMC board compatible was renamed in 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>
>> Acked-by: Rob Herring <robh@kernel.org>
>>
>> ---
>>
>> Changes since v2:
>> 1. Fix typo in commit msg.
>> 2. Add Acks.
>>
>> Changes since v1:
>> 1. Use proper qcom compatible.
>
> Andrew, Joel,
>
> Do you have any more comments on this patch? Do you plan to pick it up?
> 5 weeks passed..
Sorry, things have been a bit complicated recently. Looks okay to me,
but Joel needs to pick it up.
Acked-by: Andrew Jeffery <andrew@aj.id.au>
next prev parent reply other threads:[~2022-09-23 0:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 6:29 Krzysztof Kozlowski
2022-09-22 6:49 ` Krzysztof Kozlowski
2022-09-23 0:01 ` Andrew Jeffery [this message]
2022-10-18 13:39 ` 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=c5acf780-7a9d-442c-a41c-efc69e5d0ed3@app.fastmail.com \
--to=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=quic_jaehyoo@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=robh@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®