[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f80ea2fa-1003-48ae-bf57-df388ba1963b@quicinc.com>
Date: Thu, 5 Jun 2025 09:04:53 +0530
From: Praveen Talari <quic_ptalari@...cinc.com>
To: Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
Greg Kroah-Hartman
<gregkh@...uxfoundation.org>,
Jiri Slaby <jirislaby@...nel.org>, Rob Herring
<robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley
<conor+dt@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio
<konradybcio@...nel.org>,
<linux-arm-msm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-serial@...r.kernel.org>, <devicetree@...r.kernel.org>
CC: <psodagud@...cinc.com>, <djaggi@...cinc.com>, <quic_msavaliy@...cinc.com>,
<quic_vtanuku@...cinc.com>, <quic_arandive@...cinc.com>,
<quic_mnaresh@...cinc.com>, <quic_shazhuss@...cinc.com>
Subject: Re: [PATCH v5 6/8] serial: qcom-geni: move clock-rate logic to
separate function
Hi Bryan,
Thank you for your inputs.
On 6/5/2025 5:19 AM, Bryan O'Donoghue wrote:
> On 04/06/2025 18:11, Praveen Talari wrote:
>>> Separate this stuff out.
>>>
>>> Your code should match the commit log. If you want to convert %u to
>>> %lu make a patch to do that, even if it seems trivial, it is better
>>> to make granular submissions.
>>
>> It comes under newly added API. Do we still need to make separate patch?
>
> Best practice is to split this stuff up.
We can avoid this change by using unsigned int instead of unsigned long
in newly added API function params.
Will fix in next version.
Thanks,
Praveen Talari
>
> If your commit log says "I'm moving code" then it should _only_ move
> code, don't sneak any other changes in, no matter how seemingly innocuous.
>
> ---
> bod
Powered by blists - more mailing lists