lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <fc8b2845-5c1e-4f4f-962a-b1b0009114ba@oss.qualcomm.com>
Date: Mon, 29 Sep 2025 09:27:43 +0530
From: Taniya Das <taniya.das@....qualcomm.com>
To: Krzysztof Kozlowski <krzk@...nel.org>,
        Pankaj Patil <pankaj.patil@....qualcomm.com>
Cc: Bjorn Andersson <andersson@...nel.org>,
        Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley
 <conor+dt@...nel.org>, linux-arm-msm@...r.kernel.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 22/24] arm64: dts: qcom: glymur: Add display clock
 controller device



On 9/25/2025 1:48 PM, Krzysztof Kozlowski wrote:
> On Thu, 25 Sept 2025 at 15:34, Pankaj Patil
> <pankaj.patil@....qualcomm.com> wrote:
>>
>> From: Taniya Das <taniya.das@....qualcomm.com>
>>
>> Support the display clock controller for GLYMUR SoC.
> 
> One clock controller is not a separate commit.
> 
> Stop inflating patch count, you just makes it difficult for us to see
> complete picture.
> 

Sorry about that Krzysztof. As the display clock controller was enabled
later point of time probably it was kept as a separate patch and not
merged.

> Is this somehow for LWN stats? That's why one node per patch?
> 

That is definitely not the intention. As it was enabled later, it was
left as a separate patch.

-- 
Thanks,
Taniya Das


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ