On Mon, Sep 29, 2025 at 07:24:32PM +0200, Kory Maincent wrote: > This resyncs us with the version found in v6.17 of the Linux kernel with > the following exceptions: > - Keep our u-boot specific tests / code area. > - Keep the location of our checkpatch.rst > - Change the "use strscpy" test as we don't have that to strlcpy > - Keep debug/printf in the list for $logFunctions > - Keep checks to "env" files > > This also syncs the spdxcheck.py tool and all the associated > documentation. > > Signed-off-by: Kory Maincent <[email protected]>
I forgot to mention: commit 0fd7ee0306a88bd99d3820167fa45a7ee6fbc1e1 Author: Tom Rini <[email protected]> Date: Wed Feb 26 09:33:45 2025 -0600 scripts/checkpatch.pl: Upgrade IS_ENABLED_CONFIG to error for U-Boot A problem we have today is that some instances of IS_ENABLED(FOO) have crept in to the code. This is in turn because with checkpatch.pl this is only a warning and not an error, so they were overlooked. And looking deeper, in the Linux kernel this pattern is allowed because IS_ENABLED(DEFINED_FLAG) is allowed if discouraged and a quick skim of the instances I saw in the current kernel follow this pattern. In U-Boot however, this is not allowed, so bump to an error. Signed-off-by: Tom Rini <[email protected]> earlier, sorry. But it's easy to not undo this change, so barring other comments I'll just fix that when applying. Thanks for doing the resync! -- Tom
signature.asc
Description: PGP signature
