From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: YAMANE Toshiaki <yamanetoshi@gmail.com>
Cc: Greg Kroah-Hartman <greg@kroah.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] staging/media: Fix trailing statements should be on next line in go7007/go7007-fw.c
Date: Fri, 21 Dec 2012 18:43:11 -0200 [thread overview]
Message-ID: <20121221184311.2da34111@redhat.com> (raw)
In-Reply-To: <1352115573-8321-1-git-send-email-yamanetoshi@gmail.com>
Em Mon, 5 Nov 2012 20:39:33 +0900
YAMANE Toshiaki <yamanetoshi@gmail.com> escreveu:
> fixed below checkpatch error.
> - ERROR: trailing statements should be on next line
>
> Signed-off-by: YAMANE Toshiaki <yamanetoshi@gmail.com>
> ---
> drivers/staging/media/go7007/go7007-fw.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/staging/media/go7007/go7007-fw.c b/drivers/staging/media/go7007/go7007-fw.c
> index f99c05b..cfce760 100644
> --- a/drivers/staging/media/go7007/go7007-fw.c
> +++ b/drivers/staging/media/go7007/go7007-fw.c
> @@ -725,7 +725,8 @@ static int vti_bitlen(struct go7007 *go)
> {
> unsigned int i, max_time_incr = go->sensor_framerate / go->fps_scale;
>
> - for (i = 31; (max_time_incr & ((1 << i) - 1)) == max_time_incr; --i);
> + for (i = 31; (max_time_incr & ((1 << i) - 1)) == max_time_incr; --i)
> + ;
Nah, this doesn't sound right to me. IMO, in this specific case,
checkpatch.pl did a bad job.
At least on my eyes, the first line is easier to read than the other
two ones.
> return i + 1;
> }
>
Regards,
Mauro
next prev parent reply other threads:[~2012-12-21 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 11:38 [PATCH 1/2] staging/media: Use dev_ printks in go7007/go7007-fw.c YAMANE Toshiaki
2012-11-05 11:39 ` [PATCH 2/2] staging/media: Fix trailing statements should be on next line " YAMANE Toshiaki
2012-12-21 20:43 ` Mauro Carvalho Chehab [this message]
2012-12-22 7:20 ` 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=20121221184311.2da34111@redhat.com \
--to=mchehab@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=yamanetoshi@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.