Hey,
This breaks using patman for linux as it's check-patch has no clue about `--u-boot` :). I'm not sure if people using patman for linux patches is meant to be a supported use-case though (the documentation seems to indicate it is)
On Wed, 2022-12-21 at 00:28 +0000, Simon Glass wrote:
This resolves 10 out of 11 test failures seen when running './patman test' from the 'tools/patman' subdirectory. This was caused by the .checkpatch.conf configuration file at the root of the project not being picked up. Make the test suite of patman independent from it by always invoking the checkpatch.pl script with the minimally required arguments for the test suite to pass.
Reviewed-by: Simon Glass sjg@chromium.org Signed-off-by: Maxim Cournoyer maxim.cournoyer@savoirfairelinux.com
Changes in v3:
- Fix typo in commit message
Changes in v2:
- Reword the commit message with a better explanation of the problem
- Add the '--strict' argument to script invocation
tools/patman/checkpatch.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to u-boot-dm/next, thanks!