mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jaswinder Singh Rajput" <jaswinderlinux@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	apw@canonical.com, davej@redhat.com,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: scripts/checkpatch.pl : undefined value as an ARRAY reference
Date: Wed, 7 Jan 2009 19:04:06 +0530	[thread overview]
Message-ID: <3f9a31f40901070534t4442fb97vf8ed381c63b6354f@mail.gmail.com> (raw)
In-Reply-To: <20090107130415.GC3529@elte.hu>

On Wed, Jan 7, 2009 at 6:34 PM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Jaswinder Singh Rajput <jaswinderlinux@gmail.com> wrote:
>
>> Hello Andy,
>>
>> On -tip git I am getting this error:
>>
>> $ ./scripts/checkpatch.pl 000*
>> Can't use an undefined value as an ARRAY reference at
>> ./scripts/checkpatch.pl line 451.
>>
>> But earlier it was working great. Is this a feature or a bug.
>
> bug.
>
> One for the akpm bucket i think, Andrew pushed v26 checkpatch to Linus
> yesterday:
>
> 57b9c6d: checkpatch: version: 0.26
> 21caa13: checkpatch: fix the perlcritic errors
> 2b6db5c: checkpatch: struct file_operations should normally be const
> b53c8e1: checkpatch: ensure we actually detect if assignments split across lines
> 2d1bafd: checkpatch: do not report nr_static as a static declaration
> 4635f4f: checkpatch: track #ifdef/#else/#endif when tracking blocks
> 8b1b337: checkpatch: fix continuation detection when handling spacing on operators
> 8054576: checkpatch: loosen spacing on typedef function checks
> 080ba92: checkpatch: try to catch missing VMLINUX_SYMBOL() in vmlinux.lds.h
> 86f9d05: checkpatch: allow parentheses on return for comparisons
> 1e85572: checkpatch: Add warning for p0-patches
> 2a5a2c2: checkpatch: update copyrights
> 50a7dcf: checkpatch: version: 0.25
> 6586386: checkpatch: dissallow spaces between stars in pointer types
> fae17da: checkpatch: comment ends inside strings is most likely not an open comment
> 8e761b0: checkpatch: detect multiple bitfield declarations
> 5fe3af1: checkpatch: __weak is an official attribute
> 383099f: checkpatch: structure member assignments are not complex
> 83242e0: checkpatch: widen implied comment detection to allow multiple stars
> 721c1cb: checkpatch: comment detection may miss an implied comment on the last hunk
> 691d77b6: checkpatch: add checks for in_atomic()
>
> one of those is causing this new warning.
>

it seems error to me :

./scripts/checkpatch.pl
0007-x86-smp.h-move-boot_cpu_id-declartion-to-cpu.h.patch
Can't use an undefined value as an ARRAY reference at
./scripts/checkpatch.pl line 453.

yesterday it was working great.

Thanks
--
JSR

  reply	other threads:[~2009-01-07 13:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 12:54 Jaswinder Singh Rajput
2009-01-07 13:04 ` Ingo Molnar
2009-01-07 13:34   ` Jaswinder Singh Rajput [this message]
2009-01-07 13:07 ` Andy Whitcroft
2009-01-07 13:27   ` Jaswinder Singh Rajput
2009-01-07 23:50     ` Andy Whitcroft
2009-01-08  4:40       ` Jaswinder Singh Rajput
2009-01-08 14:54         ` Ingo Molnar
2009-01-08 16:25           ` Andy Whitcroft

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3f9a31f40901070534t4442fb97vf8ed381c63b6354f@mail.gmail.com \
    --to=jaswinderlinux@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®