public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* checkpatch.pl error: Use of uninitialized value $max (line 3407,3410)
@ 2013-01-10 19:18 Guenter Roeck
  2013-01-10 19:45 ` Joe Perches
  0 siblings, 1 reply; 2+ messages in thread
From: Guenter Roeck @ 2013-01-10 19:18 UTC (permalink / raw)
  To: linux-kernel; +Cc: Andy Whitcroft, Joe Perches

Hi all,

I get the following error when running checkpatch.pl:

scripts/checkpatch.pl -f drivers/hwmon/da9055-hwmon.c
Use of uninitialized value $max in string eq at scripts/checkpatch.pl line 3407.
Use of uninitialized value $max in pattern match (m//) at scripts/checkpatch.pl line 3410.
total: 0 errors, 0 warnings, 336 lines checked

drivers/hwmon/da9055-hwmon.c has no obvious style problems and is ready for
submission.

The checkpatch code creating the error was introduced with commit 4a273195
(checkpatch: check usleep_range() arguments).

Is this a but in checkpatch, or is something wrong in my environment ?

Thanks,
Guenter

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: checkpatch.pl error: Use of uninitialized value $max (line 3407,3410)
  2013-01-10 19:18 checkpatch.pl error: Use of uninitialized value $max (line 3407,3410) Guenter Roeck
@ 2013-01-10 19:45 ` Joe Perches
  0 siblings, 0 replies; 2+ messages in thread
From: Joe Perches @ 2013-01-10 19:45 UTC (permalink / raw)
  To: Guenter Roeck; +Cc: linux-kernel, Andy Whitcroft, Andrew Morton

On Thu, 2013-01-10 at 11:18 -0800, Guenter Roeck wrote:
> Hi all,

Hi Guenter.

> I get the following error when running checkpatch.pl:
> 
> scripts/checkpatch.pl -f drivers/hwmon/da9055-hwmon.c
> Use of uninitialized value $max in string eq at scripts/checkpatch.pl line 3407.
> Use of uninitialized value $max in pattern match (m//) at scripts/checkpatch.pl line 3410.

[]

> The checkpatch code creating the error was introduced with commit 4a273195
> (checkpatch: check usleep_range() arguments).

> Is this a but in checkpatch, or is something wrong in my environment ?

Yes, it's a checkpatch bug, ignore it for now.
You'd also get it if you had a memset.

It's a problem with the $Float test

I believe this should fix it.

I haven't tested it much though.

 scripts/checkpatch.pl | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 9de3a69..3d0f577 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -230,12 +230,12 @@ our $Inline	= qr{inline|__always_inline|noinline};
 our $Member	= qr{->$Ident|\.$Ident|\[[^]]*\]};
 our $Lval	= qr{$Ident(?:$Member)*};
 
-our $Float_hex	= qr{(?i:0x[0-9a-f]+p-?[0-9]+[fl]?)};
-our $Float_dec	= qr{(?i:((?:[0-9]+\.[0-9]*|[0-9]*\.[0-9]+)(?:e-?[0-9]+)?[fl]?))};
-our $Float_int	= qr{(?i:[0-9]+e-?[0-9]+[fl]?)};
+our $Float_hex	= qr{(?i)0x[0-9a-f]+p-?[0-9]+[fl]?};
+our $Float_dec	= qr{(?i)(?:[0-9]+\.[0-9]*|[0-9]*\.[0-9]+)(?:e-?[0-9]+)?[fl]?};
+our $Float_int	= qr{(?i)[0-9]+e-?[0-9]+[fl]?};
 our $Float	= qr{$Float_hex|$Float_dec|$Float_int};
-our $Constant	= qr{(?:$Float|(?i:(?:0x[0-9a-f]+|[0-9]+)[ul]*))};
-our $Assignment	= qr{(?:\*\=|/=|%=|\+=|-=|<<=|>>=|&=|\^=|\|=|=)};
+our $Constant	= qr{$Float|(?i)(?:0x[0-9a-f]+|[0-9]+)[ul]*};
+our $Assignment	= qr{\*\=|/=|%=|\+=|-=|<<=|>>=|&=|\^=|\|=|=};
 our $Compare    = qr{<=|>=|==|!=|<|>};
 our $Operators	= qr{
 			<=|>=|==|!=|



^ permalink raw reply related	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2013-01-10 19:45 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-10 19:18 checkpatch.pl error: Use of uninitialized value $max (line 3407,3410) Guenter Roeck
2013-01-10 19:45 ` Joe Perches

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox