From: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
To: PINTU KUMAR <pintu_agarwal@yahoo.com>,
Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>
Cc: anish singh <anish198519851985@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [checkpatch] - Confusion
Date: Tue, 11 Jun 2013 17:54:32 -0700 [thread overview]
Message-ID: <8a2ec29d-e6d8-44ed-a70d-2273848706ce@VA3EHSMHS029.ehs.local> (raw)
In-Reply-To: <1370890140.99216.YahooMailNeo@web160102.mail.bf1.yahoo.com>
Hi Pintu,
On Mon, Jun 10, 2013 at 11:49:00AM -0700, PINTU KUMAR wrote:
> >________________________________
> > From: anish singh <anish198519851985@gmail.com>
> >To: PINTU KUMAR <pintu_agarwal@yahoo.com>
> >Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>; "linux-mm@kvack.org" <linux-mm@kvack.org>
> >Sent: Sunday, 9 June 2013 10:58 PM
> >Subject: Re: [checkpatch] - Confusion
> >
> >
> >On Mon, Jun 10, 2013 at 11:21 AM, PINTU KUMAR <pintu_agarwal@yahoo.com> wrote:
> >> Hi,
> >>
> >> I wanted to submit my first patch.
> >> But I have some confusion about the /scripts/checkpatch.pl errors.
> >>
> >> After correcting some checkpatch errors, when I run checkpatch.pl, it showed me 0 errors.
> >> But when I create patches are git format-patch, it is showing me 1 error.
> >did you run the checkpatch.pl on the file which gets created
> >after git format-patch?
> >If yes, then I think it is not necessary.You can use git-am to apply
> >your own patch on a undisturbed file and if it applies properly then
> >you are good to go i.e. you can send your patch.
>
> Yes, first I ran checkpatch directly on the file(mm/page_alloc.c) and fixed all the errors.
> It showed me (0) errors.
> Then I created a patch using _git format-patch_ and ran checkpatch again on the created patch.
> But now it is showing me 1 error.
> According to me this error is false positive (irrelevant), because I did not change anything related to the error and also the similar change already exists somewhere else too.
> Do you mean, shall I go ahead and submit the patch with this 1 error??
> ERROR: need consistent spacing around '*' (ctx:WxV)
>
> #153: FILE: mm/page_alloc.c:5476:
> +int min_free_kbytes_sysctl_handler(ctl_table *table, int write,
Rather a shot into the dark, but it looks like checkpatch is
misinterpreting 'ctl_table' as an arithmetic operand instead of a type.
I don't know how checkpatch learns about types created by typedefs, but
my guess is, that this line
typedef struct ctl_table ctl_table; (include/linux/sysctl.h)
is not correctly picked up by checkpatch.
So, I assume this actually is a false positive.
Sören
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-06-12 0:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 5:51 PINTU KUMAR
2013-06-10 5:58 ` anish singh
2013-06-10 18:49 ` PINTU KUMAR
2013-06-12 0:54 ` Sören Brinkmann [this message]
2013-06-12 4:15 ` Joe Perches
2013-06-12 4:48 ` Joe Perches
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=8a2ec29d-e6d8-44ed-a70d-2273848706ce@VA3EHSMHS029.ehs.local \
--to=soren.brinkmann@xilinx.com \
--cc=anish198519851985@gmail.com \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pintu_agarwal@yahoo.com \
/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