From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Yinbo Zhu <zhuyinbo@loongson.cn>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Jianmin Lv <lvjianmin@loongson.cn>,
Yang Li <yang.lee@linux.alibaba.com>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, loongarch@lists.linux.dev
Subject: Re: [PATCH v5 1/3] dt-bindings: clock: add loongson-2 clock include file
Date: Wed, 2 Nov 2022 12:17:29 -0400 [thread overview]
Message-ID: <abc9ed33-26d2-b850-8c7a-78cb1735ddb2@linaro.org> (raw)
In-Reply-To: <2bd0f05d-a5c4-3c5c-ccbc-3e3385cc0a1d@loongson.cn>
On 28/10/2022 22:54, Yinbo Zhu wrote:
>
>
> 在 2022/10/28 下午7:43, Krzysztof Kozlowski 写道:
>> On 27/10/2022 22:55, Yinbo Zhu wrote:
>>> This file defines all Loongson-2 SoC clock indexes, it should be
>>> included in the device tree in which there's device using the
>>> clocks.
>>>
>>> Signed-off-by: Yinbo Zhu <zhuyinbo@loongson.cn>
>>> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>> ---
>>> Change in v5:
>>> 1. Replace loongson2/Loongson2 with loongson-2/Loongson-2.
>>> 2. Replace soc with SoC.
>>>
>>
>> Where is the rest of the changelog?
> What you're asking is where the replacement string is located. it was
> in commit log.
I am asking why there is only v5 changelog? Where is v4, v3, v2?
Best regards,
Krzysztof
prev parent reply other threads:[~2022-11-02 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 2:55 Yinbo Zhu
2022-10-28 2:55 ` [PATCH v5 2/3] clk: clk-loongson2: add clock controller driver support Yinbo Zhu
2022-10-28 2:55 ` [PATCH v5 3/3] dt-bindings: clock: add loongson-2 clock Yinbo Zhu
2022-10-28 11:43 ` [PATCH v5 1/3] dt-bindings: clock: add loongson-2 clock include file Krzysztof Kozlowski
2022-10-29 2:54 ` Yinbo Zhu
2022-11-02 16:17 ` Krzysztof Kozlowski [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=abc9ed33-26d2-b850-8c7a-78cb1735ddb2@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=chenhuacai@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=lvjianmin@loongson.cn \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=yang.lee@linux.alibaba.com \
--cc=zhuyinbo@loongson.cn \
/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®