From: Yijie Yang <yijie.yang@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Georgi Djakov <djakov@kernel.org>, Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v2] dt-bindings: interconnect: qcom-bwmon: Add Maili cpu-bwmon compatible
Date: Tue, 11 Aug 2026 17:10:59 +0800 [thread overview]
Message-ID: <ef0b034b-a969-409e-a2c2-4c7fa95b57c3@oss.qualcomm.com> (raw)
In-Reply-To: <d8d89181-bc76-4023-87fd-02e85f5c8d49@kernel.org>
On 8/11/2026 4:57 PM, Krzysztof Kozlowski wrote:
> On 11/08/2026 10:53, Yijie Yang wrote:
>>> ---
>>> base-commit: 550604d6c9b9efc8d068aff94dc301694a7afdee
>>> change-id: 20260512-bwmon-ecb43fda63c9
>>>
>>> Best regards,
>>> --
>>> Yijie Yang <yijie.yang@oss.qualcomm.com>
>>
>> Sorry for missing the previous Reviewed-by and Acked-by tags. I'll send
>> a v3 update to include them.
>>
>
> So how is this resend actually helping to get the code merged. :/
>
> Best regards,
> Krzysztof
Fair point. The patch itself hasn't changed. I only realized after
sending the RESEND that I had dropped the previously received
Reviewed-by and Acked-by tags. I won't spinning a new version just for that.
Previously received trailers:
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Reviewed-by: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
--
Best Regards,
Yijie
prev parent reply other threads:[~2026-08-11 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 8:46 [PATCH RESEND v2] dt-bindings: interconnect: qcom-bwmon: Add Maili cpu-bwmon compatible Yijie Yang
2026-08-11 8:50 ` Krzysztof Kozlowski
2026-08-11 8:53 ` Yijie Yang
2026-08-11 8:57 ` Krzysztof Kozlowski
2026-08-11 9:10 ` Yijie Yang [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=ef0b034b-a969-409e-a2c2-4c7fa95b57c3@oss.qualcomm.com \
--to=yijie.yang@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.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