[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d20c9b08-4f9a-43d0-91ad-b971fdd19422@quicinc.com>
Date: Wed, 6 Mar 2024 13:30:03 +0530
From: Kathiravan Thirumoorthy <quic_kathirav@...cinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Viresh Kumar
<viresh.kumar@...aro.org>
CC: Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio
<konrad.dybcio@...aro.org>,
Rob Herring <robh@...nel.org>,
Krzysztof
Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley
<conor+dt@...nel.org>, Ilia Lin <ilia.lin@...nel.org>,
"Rafael J. Wysocki"
<rafael@...nel.org>,
<linux-arm-msm@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-pm@...r.kernel.org>
Subject: Re: [PATCH 3/3] cpufreq: qcom-nvmem: add support for IPQ5321
On 3/6/2024 12:52 PM, Krzysztof Kozlowski wrote:
> 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.
Does the "necessary acks" refers for to the acks from Qualcomm SoC
maintainers? Sorry, I wasn't aware of that. That's why I mentioned
"Sorry, I'm not sure on this..." couple of lines below.
>
>> 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.
Understood. Will take care in future.
>
> Best regards,
> Krzysztof
>
Powered by blists - more mailing lists