[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2784c69e-898d-3a40-a0f7-b7769a57980b@csgroup.eu>
Date: Thu, 19 Aug 2021 13:50:57 +0200
From: Christophe Leroy <christophe.leroy@...roup.eu>
To: Lukas Bulwahn <lukas.bulwahn@...il.com>,
Paul Mackerras <paulus@...abs.org>,
Michael Ellerman <mpe@...erman.id.au>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Michael Neuling <mikey@...ling.org>,
Anshuman Khandual <anshuman.khandual@....com>,
kvm-ppc@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org
Cc: stable@...r.kernel.org, kernel-janitors@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] Kconfig symbol fixes on powerpc
Le 19/08/2021 à 13:39, Lukas Bulwahn a écrit :
> Dear powerpc maintainers,
>
> The script ./scripts/checkkconfigsymbols.py warns on invalid references to
> Kconfig symbols (often, minor typos, name confusions or outdated references).
>
> This patch series addresses all issues reported by
> ./scripts/checkkconfigsymbols.py in ./drivers/usb/ for Kconfig and Makefile
> files. Issues in the Kconfig and Makefile files indicate some shortcomings in
> the overall build definitions, and often are true actionable issues to address.
>
> These issues can be identified and filtered by:
>
> ./scripts/checkkconfigsymbols.py | grep -E "arch/powerpc/.*(Kconfig|Makefile)" -B 1 -A 1
>
> After applying this patch series on linux-next (next-20210817), the command
> above yields just two false positives (SHELL, r13) due to tool shortcomings.
>
> As these two patches are fixes, please consider if they are suitable for
> backporting to stable.
>
> v1 -> v2:
> Followed Christophe Leroy's comment and drop the obsolete select.
>
No need to change anything now, but as your two patches are completely independent, you could have
submitted them separately. That would have avoided to resend both when changing the first one only.
Powered by blists - more mailing lists