From: Joe Perches <joe@perches.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Andy Whitcroft <apw@canonical.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: checkpatch complaint
Date: Wed, 08 Feb 2012 15:42:14 -0800 [thread overview]
Message-ID: <1328744534.6909.2.camel@joe2Laptop> (raw)
In-Reply-To: <4F32E062.1020709@broadcom.com>
On Wed, 2012-02-08 at 21:51 +0100, Arend van Spriel wrote:
> checkpatch complains on code below and I must overlook something or
> checkpatch gives a false negative/positive/whatever:
>
> #define IFPTR(usb, idx) ((usb)->actconfig->interface[(idx)])
> #define IFALTS(usb, idx) (IFPTR((usb), (idx))->altsetting[0])
> #define IFDESC(usb, idx) IFALTS((usb), (idx)).desc
> #define IFEPDESC(usb, idx, ep) \
> (IFALTS((usb), (idx)).endpoint[(ep)]).desc
>
> checkpatch errors:
> ERROR: Macros with complex values should be enclosed in parenthesis
> #169: FILE: drivers/net/wireless/brcm80211/brcmfmac/usb.c:58:
> +#define IFDESC(usb, idx) (IFALTS((usb), (idx))).desc
>
> ERROR: Macros with complex values should be enclosed in parenthesis
> #170: FILE: drivers/net/wireless/brcm80211/brcmfmac/usb.c:59:
> +#define IFEPDESC(usb, idx, ep) ((IFALTS((usb),
> (idx))).endpoint[(ep)]).desc
>
> Any ideas? I tried extra parenthesis around IFALTS but that does not
> resolve it.
I think the entries should be surround by ()
I think it's reasonable too.
I tried:
$ cat cp.c
#define IFPTR(usb, idx) ((usb)->actconfig->interface[(idx)])
#define IFALTS(usb, idx) (IFPTR((usb), (idx))->altsetting[0])
#define IFDESC(usb, idx) (IFALTS((usb), (idx)).desc)
#define IFEPDESC(usb, idx, ep) ((IFALTS((usb), (idx)).endpoint[(ep)]).desc)
$ ./scripts/checkpatch.pl -f cp.c
total: 0 errors, 0 warnings, 5 lines checked
cp.c has no obvious style problems and is ready for submission.
next prev parent reply other threads:[~2012-02-08 23:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 20:51 checkpatch complaint Arend van Spriel
2012-02-08 23:42 ` Joe Perches [this message]
2012-02-09 5:05 ` Guenter Roeck
2012-02-09 10:20 ` Bernd Petrovitsch
2012-02-09 10:06 ` Dan Carpenter
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=1328744534.6909.2.camel@joe2Laptop \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=arend@broadcom.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.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