[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4f958a0c7c0aa2fce613371348477c002aa58e90.camel@perches.com>
Date: Thu, 01 Sep 2022 11:49:24 -0400
From: Joe Perches <joe@...ches.com>
To: Mickaël Salaün <mic@...ikod.net>,
Andy Whitcroft <apw@...onical.com>
Cc: Dwaipayan Ray <dwaipayanray1@...il.com>,
Lukas Bulwahn <lukas.bulwahn@...il.com>,
Shuah Khan <shuah@...nel.org>, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org
Subject: Re: [RFC PATCH v1] checkpatch: Handle FILE pointer type
On Thu, 2022-09-01 at 16:59 +0200, Mickaël Salaün wrote:
> When using a "FILE *" type, checkpatch considers this an error. Fix
> this by explicitly defining "FILE" as a common type.
[]
> Another error may be throw when we use FIXTURE_{DATA,VARIANT}() structs,
> as defined in kselftest_harness.h .
[]
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -576,10 +576,17 @@ our $typeKernelTypedefs = qr{(?x:
> (?:__)?(?:u|s|be|le)(?:8|16|32|64)|
> atomic_t
> )};
> +our $typeStdioTypedefs = qr{(?x:
> + FILE
> +)};
I'm fine with this.
> +# our $typeKselftestHarnessTypedefs = qr{(?x:
> +# FIXTURE_(?:DATA|VARIANT)\($Ident\)
> +# )};
But not this. Random userspace typedefs should likely
be kept in some local version of checkpatch.
Or maybe add a command line option like --additional_typedefs=<file>.
> our $typeTypedefs = qr{(?x:
> $typeC99Typedefs\b|
> $typeOtherOSTypedefs\b|
> - $typeKernelTypedefs\b
> + $typeKernelTypedefs\b|
> + $typeStdioTypedefs\b
> )};
Powered by blists - more mailing lists