linux-kernel - Re: [PATCH v4 2/4] soc: qcom: llcc-qcom: Add support for LLCC V6

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <a1ecf255-f8c5-4f3c-ace5-793171a5ab87@oss.qualcomm.com>
Date: Mon, 12 May 2025 13:53:37 -0700
From: Melody Olvera <melody.olvera@....qualcomm.com>
To: Bjorn Andersson <andersson@...nel.org>
Cc: Konrad Dybcio <konradybcio@...nel.org>, Conor Dooley <conor@...nel.org>,
        Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley <conor+dt@...nel.org>,
        Satya Durga Srinivasu Prabhala <quic_satyap@...cinc.com>,
        Trilok Soni <quic_tsoni@...cinc.com>, linux-arm-msm@...r.kernel.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 2/4] soc: qcom: llcc-qcom: Add support for LLCC V6



On 5/12/2025 10:45 AM, Melody Olvera wrote:
>
>
> On 5/9/2025 3:12 PM, Bjorn Andersson wrote:
>> On Mon, Apr 14, 2025 at 04:21:51PM -0700, Melody Olvera wrote:
>>> Add support for LLCC V6. V6 adds several additional usecase IDs,
>>> rearrages several registers and offsets, and supports slice IDs
>>> over 31, so add a new function for programming LLCC V6.
>>>
>> Can you please fix up the checkpatch warnings in this patch?
>>
>
> Apologies; I'm not seeing checkpatch warnings on this patch. I'm on 
> tip of linux-next/master.
> I ran b4 prep --check, exported the patches with git format-patch and 
> tried running each
> through checkpatch.pl individually, ran dt_bindings_check and 
> CHECK_DTBS=y and still
> not seeing any problems. Am I missing something here?

Was missing the --strict flag. Will fix.

Thanks,
Melody