From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Kathiravan Thirumoorthy <quic_kathirav@quicinc.com>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Ilia Lin <ilia.lin@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 3/3] cpufreq: qcom-nvmem: add support for IPQ5321
Date: Wed, 6 Mar 2024 08:22:47 +0100 [thread overview]
Message-ID: <87e0aa08-9176-495d-b799-c2ddb53c8a23@linaro.org> (raw)
In-Reply-To: <c82e4053-4cef-4010-a734-4dc537574201@quicinc.com>
On 06/03/2024 05:40, Kathiravan Thirumoorthy wrote:
>>>
>>> Applied. Thanks.
>>
>> Dropped since the previous commit it required too. Can we get the
>> necessary acks for me to pick those ?
>>
>
> Sorry for not mentioning the dependencies.
>
> patch 1/3 and 2/3 are already has the R-b and A-b tags. But typically
From whom? Not from Qualcomm SoC maintainers.
> those patches will go via qcom tree. Do you want to pick it via your
> tree? Sorry, I'm not sure on this...
Your cover letter or patch changelog should clearly document
dependencies, so maintainers could understand what to do with this patch.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-03-06 7:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 14:51 [PATCH 0/3] Add support for the IPQ5321 SoC Kathiravan Thirumoorthy
2024-02-28 14:51 ` [PATCH 1/3] dt-bindings: arm: qcom,ids: Add SoC ID for IPQ5321 Kathiravan Thirumoorthy
2024-02-29 14:45 ` Krzysztof Kozlowski
2024-02-28 14:51 ` [PATCH 2/3] soc: qcom: socinfo: " Kathiravan Thirumoorthy
2024-02-29 14:45 ` Krzysztof Kozlowski
2024-02-28 14:51 ` [PATCH 3/3] cpufreq: qcom-nvmem: add support " Kathiravan Thirumoorthy
2024-03-04 7:12 ` Viresh Kumar
2024-03-05 4:35 ` Viresh Kumar
2024-03-06 4:40 ` Kathiravan Thirumoorthy
2024-03-06 5:18 ` Viresh Kumar
2024-03-06 5:32 ` Viresh Kumar
2024-03-06 7:22 ` Krzysztof Kozlowski [this message]
2024-03-06 8:00 ` Kathiravan Thirumoorthy
2024-02-28 15:06 ` [PATCH 0/3] Add support for the IPQ5321 SoC Mukesh Ojha
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=87e0aa08-9176-495d-b799-c2ddb53c8a23@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ilia.lin@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_kathirav@quicinc.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=viresh.kumar@linaro.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®