[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bdcc3e48-ceee-45bf-bc4f-f0e63d44b333@linaro.org>
Date: Thu, 5 Jun 2025 00:49:11 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Praveen Talari <quic_ptalari@...cinc.com>,
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
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.
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