From: Bjorn Helgaas <helgaas@kernel.org>
To: sasa bogicevic <brutallesale@gmail.com>
Cc: rjw@rjwysocki.net, lenb@kernel.org, bhelgaas@google.com,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] drivers:pci:hotplug Fix all space prohibited before that ,
Date: Thu, 10 Dec 2015 17:24:46 -0600 [thread overview]
Message-ID: <20151210232446.GA17458@localhost> (raw)
In-Reply-To: <6CF18E87-8037-4BD5-82EE-5CCA2BCE8A75@gmail.com>
On Fri, Dec 11, 2015 at 12:07:03AM +0100, sasa bogicevic wrote:
> I wanted to start with approach one error one folder so I did “space prohibited before ,” in just hotplug folder. I used checkpatch script to see if I nailed it and the output was fine.
> When I do grep -rl I also get the same result eventhou when I look at the, for example, drivers/pci/hotplug/shpchp_ctrl.c there is no space before comma anywhere. I double checked it. I didn’t do header files unfortunately so that errors are expected I guess.
>
> ./scripts/checkpatch.pl --file --terse drivers/pci/hotplug/shpchp_ctrl.c
> drivers/pci/hotplug/shpchp_ctrl.c:190: WARNING: Block comments use * on subsequent lines
> drivers/pci/hotplug/shpchp_ctrl.c:264: WARNING: line over 80 characters
> drivers/pci/hotplug/shpchp_ctrl.c:265: WARNING: line over 80 characters
> drivers/pci/hotplug/shpchp_ctrl.c:344: ERROR: return is not a function, parentheses are not required
> drivers/pci/hotplug/shpchp_ctrl.c:359: ERROR: return is not a function, parentheses are not required
> drivers/pci/hotplug/shpchp_ctrl.c:439: WARNING: Possible unnecessary 'out of memory' message
> drivers/pci/hotplug/shpchp_ctrl.c:463: WARNING: space prohibited between function name and open parenthesis '('
> drivers/pci/hotplug/shpchp_ctrl.c:478: WARNING: space prohibited between function name and open parenthesis '('
> drivers/pci/hotplug/shpchp_ctrl.c:569: WARNING: space prohibited between function name and open parenthesis '('
> drivers/pci/hotplug/shpchp_ctrl.c:626: WARNING: space prohibited between function name and open parenthesis ‘('
> total: 2 errors, 8 warnings, 730 lines checked
>
> I used objdiff to record and see if I didn’t change anything and I got no output so I guess all is good, don’t know why grep finds “ ,” it is a mystery to me since I am on my working branch, looking at a file and it is not there. Can you also take a look on your side ?
>
> I wanted to do one small thing and when I see that it is good and accepted from you then do all warnings and errors one by one.
OK, makes sense. I think you're on the right track, and if you extend
this patch to all of drivers/pci, I'll apply it.
I see you found the lines that checkpatch didn't complain about.
Maybe checkpatch doesn't look at things inside quoted strings? That's
just a guess; I don't use checkpatch regularly.
If you plan to do other things, e.g., removing spaces between the
function name and open parenthesis, I'd like to have all the "white
space-only" changes in a single patch.
Bjorn
next prev parent reply other threads:[~2015-12-10 23:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 10:40 [PATCH] drivers:pci:hotplug Fix all space prohibited before that , Bogicevic Sasa
2015-12-10 22:47 ` Bjorn Helgaas
2015-12-10 23:07 ` sasa bogicevic
2015-12-10 23:24 ` Bjorn Helgaas [this message]
2015-12-10 23:28 ` sasa bogicevic
2015-12-10 23:11 ` sasa bogicevic
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=20151210232446.GA17458@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=brutallesale@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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