From: hugo@carfax.org.uk (Hugo Mills)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [PATCH] staging: Fix spacing between function name and parentheses
Date: Sat, 11 Oct 2014 14:52:40 +0100 [thread overview]
Message-ID: <20141011135239.GL10301@carfax.org.uk> (raw)
In-Reply-To: <54393425.1040409@gmail.com>
On Sat, Oct 11, 2014 at 09:44:05AM -0400, nick wrote:
> Thank you for your help, I'll study the code and see what I can do
> about it. Do you have any suggestions of how to fix this checkpatch
> warning?
Ignore it. The checker has clearly triggered on a false positive --
this is not a function call, and should not be held to that standard.
(Take a look at where the macro is actually used, to see what's going
on here). Move on to find something more interesting to fix.
Hugo.
> Nick
>
> On 14-10-11 05:53 AM, Kristofer Hallin wrote:
> > Even if you use checkpath you _should_ understand what you are changing.
> > The output of checkpatch merely there to help.
> >
> > In this case you can see that this is a macro just a few lines up in the
> > code.
> > On 11 Oct 2014 11:46, "Sudip Mukherjee" <sudipm.mukherjee@gmail.com> wrote:
> >
> >> I agree. But in my opinion checkpatch is here to help us fix style
> >> problems , but we should not blindly act on checkpatch warnings.
> >>
> >> thanks
> >> sudip
> >>
> >> On Sat, Oct 11, 2014 at 1:57 PM, Peter Senna Tschudin
> >> <peter.senna@gmail.com> wrote:
> >>> I think that, in this case, checkpatch.pl contributed:
> >>>
> >>> $ ./scripts/checkpatch.pl -f drivers/staging/octeon-usb/octeon-hcd.c
> >>> WARNING: space prohibited between function name and open parenthesis '('
> >>> #415: FILE: drivers/staging/octeon-usb/octeon-hcd.c:415:
> >>> + if (c.s.field op (value)) {
> >> \
> >>>
> >>>
> >>> On Sat, Oct 11, 2014 at 8:11 AM, Dave Tian <dave.jing.tian@gmail.com>
> >> wrote:
> >>>> Agreed - that is why I mentioned the patch is neither right nor useful:)
> >>>>
> >>>> -daveti
> >>>>
> >>>>
> >>>> On Oct 11, 2014, at 2:08 PM, Sudip Mukherjee <
> >> sudipm.mukherjee at gmail.com> wrote:
> >>>>
> >>>>> Hi Dave,
> >>>>> It will work. But my point of saying that was c.s.field ==(value) is
> >>>>> again not according to the style.
> >>>>>
> >>>>> thanks
> >>>>> sudip
> >>>>>
> >>>>> On Sat, Oct 11, 2014 at 10:53 AM, Dave Tian <dave.jing.tian@gmail.com>
> >> wrote:
> >>>>>> It also works as value is surrounded by (), though I do not think the
> >> patch itself is right or useful.
> >>>>>>
> >>>>>> Dave Tian
> >>>>>> dave.jing.tian at gmail.com
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Oct 11, 2014, at 12:58 PM, Sudip Mukherjee <
> >> sudipm.mukherjee at gmail.com> wrote:
> >>>>>>
> >>>>>>> On Fri, Oct 10, 2014 at 09:55:48PM -0400, Nicholas Krause wrote:
> >>>>>>>> Fixes checkpatch coding style warning about unneeded space
> >>>>>>>> between function name an parentheses.
> >>>>>>>>
> >>>>>>>> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> >>>>>>>> ---
> >>>>>>>> Untested
> >>>>>>>> drivers/staging/octeon-usb/octeon-hcd.c | 2 +-
> >>>>>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>>>>>>>
> >>>>>>>> diff --git a/drivers/staging/octeon-usb/octeon-hcd.c
> >> b/drivers/staging/octeon-usb/octeon-hcd.c
> >>>>>>>> index 5f9db4c..bbeb0cc 100644
> >>>>>>>> --- a/drivers/staging/octeon-usb/octeon-hcd.c
> >>>>>>>> +++ b/drivers/staging/octeon-usb/octeon-hcd.c
> >>>>>>>> @@ -412,7 +412,7 @@ struct octeon_hcd {
> >>>>>>>> type c;
> >> \
> >>>>>>>> while (1) {
> >> \
> >>>>>>>> c.u32 = __cvmx_usb_read_csr32(usb, address);
> >> \
> >>>>>>>> - if (c.s.field op (value)) {
> >> \
> >>>>>>>> + if (c.s.field op(value)) {
> >> \
> >>>>>>>
> >>>>>>> have you read the code before modifying it?
> >>>>>>> this is not a function.
> >>>>>>> have you seen how CVMX_WAIT_FOR_FIELD32 is being called?
> >>>>>>> on every call of CVMX_WAIT_FOR_FIELD32 op is the operator "=="
> >>>>>>> so when called the macro will be c.s.field == (value).
> >>>>>>> if your patch is applied then it will become c.s.field ==(value) ..
> >> will that be correct ?
> >>>>>>>
> >>>>>>> thanks
> >>>>>>> sudip
> >>>>>>>
> >>>>>>>> result = 0;
> >> \
> >>>>>>>> break;
> >> \
> >>>>>>>> } else if (cvmx_get_cycle() > done) {
> >> \
--
=== Hugo Mills: hugo at ... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Happiness is mandatory. Are you happy? ---
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 811 bytes
Desc: Digital signature
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20141011/a7281663/attachment-0001.bin
next prev parent reply other threads:[~2014-10-11 13:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 1:55 [PATCH] staging: Fix spacing between function name and parentheses Nicholas Krause
2014-10-11 4:58 ` Sudip Mukherjee
2014-10-11 5:23 ` Dave Tian
2014-10-11 6:08 ` Sudip Mukherjee
2014-10-11 6:11 ` Dave Tian
2014-10-11 8:27 ` Peter Senna Tschudin
2014-10-11 9:45 ` Sudip Mukherjee
2014-10-11 9:53 ` Kristofer Hallin
2014-10-11 13:44 ` nick
2014-10-11 13:46 ` Kristofer Hallin
2014-10-11 13:52 ` Hugo Mills [this message]
2014-10-11 14:17 ` nick
2014-10-11 15:25 ` karthik nayak
2014-10-11 22:18 ` nick
2014-10-12 22:34 ` Valdis.Kletnieks at vt.edu
2014-10-13 2:31 ` nick
2014-10-13 3:15 ` Valdis.Kletnieks at vt.edu
2014-10-13 4:55 ` Sudip Mukherjee
2014-10-14 15:38 ` Adrian Cornish
2014-10-14 18:11 ` Kernel Apprentice
2014-10-14 21:08 ` John de la Garza
2014-10-20 9:17 ` el_es
2014-11-02 0:34 ` Valdis.Kletnieks at vt.edu
2014-11-03 10:05 ` Bjørn Mork
2014-11-04 2:23 ` nick
2014-10-11 14:24 ` Robert P. J. Day
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=20141011135239.GL10301@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).