From: Andy Whitcroft <apw@canonical.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Andy Walls <awalls@radix.net>
Subject: Re: checkpatch is not detecting bad whitespacing when using macros on formulas
Date: Mon, 26 Oct 2009 11:20:36 +0000 [thread overview]
Message-ID: <20091026112036.GG12089@shadowen.org> (raw)
In-Reply-To: <20091011071911.54347f2b@pedra.chehab.org>
On Sun, Oct 11, 2009 at 07:19:11AM -0300, Mauro Carvalho Chehab wrote:
> Hi Andy Whitcroft,
>
> While reviewing a patch from Andy Walls, I noticed that checkpatch v 0.29
> didn't get any errors when bad whitespacing is used on some formulas:
>
> $ checkpatch.pl cx23888-ir-part2_2.patch
> total: 0 errors, 0 warnings, 1237 lines checked
>
> cx23888-ir-part2_2.patch has no obvious style problems and is ready for submission.
>
> However, there are several places at the patch like:
>
> +static inline u16 ns_to_clock_divider(unsigned int ns)
> +{
> + return count_to_clock_divider(
> + DIV_ROUND_CLOSEST(CX23888_IR_REFCLK_FREQ/1000000 * ns, 1000));
> +}
I assume the error you are pointing out is the lack of spacing round the
divide operator. Though the guidelines ask for spacing on both sides
there are cases where it has been argued that no spacing is more
appropriate. Once such case is where the expression is effectivly
generating a constant, such as that above and you will find a slew of
such uses in the kernel. As a result the checkpatch check for this
spacing is actually slightly more liberal checking for consistant
spacing on either side, spaces both sides or neither.
-apw
prev parent reply other threads:[~2009-10-26 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 10:19 checkpatch is not detecting bad whitespacing when using macros on formulas Mauro Carvalho Chehab
2009-10-11 11:01 ` Tilman Schmidt
2009-10-11 14:26 ` Mauro Carvalho Chehab
2009-10-11 22:04 ` Tilman Schmidt
2009-10-26 11:20 ` Andy Whitcroft [this message]
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=20091026112036.GG12089@shadowen.org \
--to=apw@canonical.com \
--cc=awalls@radix.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.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