linux-kernel - Re: [PATCH 3/3] clk: meson: s4: add s4 SoC clock controller driver

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: <12a2487c-6d49-af99-aa5c-edd7a2eff071@linaro.org>
Date:   Tue, 19 Jul 2022 09:29:43 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Yu Tu <yu.tu@...ogic.com>, linux-clk@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org,
        linux-amlogic@...ts.infradead.org, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
        Neil Armstrong <narmstrong@...libre.com>,
        Jerome Brunet <jbrunet@...libre.com>,
        Kevin Hilman <khilman@...libre.com>,
        Michael Turquette <mturquette@...libre.com>,
        Stephen Boyd <sboyd@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Subject: Re: [PATCH 3/3] clk: meson: s4: add s4 SoC clock controller driver

On 19/07/2022 08:58, Yu Tu wrote:
>>>>> @@ -1772,7 +1772,7 @@ M:	Jerome Brunet <jbrunet@...libre.com>
>>>>>    L:	linux-amlogic@...ts.infradead.org
>>>>>    S:	Maintained
>>>>>    F:	Documentation/devicetree/bindings/clock/amlogic*
>>>>> -F:	drivers/clk/meson/
>>>>> +F:	drivers/clk/meson/*
>>>>
>>>> Why?
>>> Warning is displayed when using checkpatch. I will correct it.
>>
>> What warning?
>   ./scripts/checkpatch.pl --strict 
> 0001-clk-meson-s4-add-s4-SoC-clock-controller-driver.patch
> WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
> If I add that strange change, I won't have this WARNING.
> Should I ignore this warning?

Yes, it's not related to the patch and the change you made looks not
correct.


Best regards,
Krzysztof