From: Joe Perches <joe@perches.com>
To: Daniel Hamacher <danielhamacher.dh@gmail.com>
Cc: greg@kroah.com, abotti@mev.co.uk, fmhess@users.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: comedi: proc.c Fixed warning and brace code style issue [kernel: linux-next: next-20130607]
Date: Fri, 07 Jun 2013 00:47:33 -0700 [thread overview]
Message-ID: <1370591253.2209.99.camel@joe-AO722> (raw)
In-Reply-To: <1370590023-5647-1-git-send-email-danielhamacher.dh@gmail.com>
On Fri, 2013-06-07 at 01:27 -0600, Daniel Hamacher wrote:
> checkpatch provided a warning on line 38. It recommended seq_puts instead of seq_printf.
> Since the return value of printf is ignored, I decided to switch to the seq_puts
> function since it is just regular character output.
> source:: http://lwn.net/Articles/22355/
>
> I also added braces on a for loop, since loops should be in braces.
> source:: Documentation/CodingStyle
>
> Signed-off-by: Daniel Hamcher <danielhamacher.dh@gmail.com>
> ---
> drivers/staging/comedi/proc.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/staging/comedi/proc.c b/drivers/staging/comedi/proc.c
> index 8ee9442..5cf19b3 100644
> --- a/drivers/staging/comedi/proc.c
> +++ b/drivers/staging/comedi/proc.c
> @@ -34,11 +34,11 @@ static int comedi_read(struct seq_file *m, void *v)
> int devices_q = 0;
> struct comedi_driver *driv;
>
> - seq_printf(m,
> - "comedi version " COMEDI_RELEASE "\n"
> - "format string: %s\n",
> - "\"%2d: %-20s %-20s %4d\", i, "
> - "driver_name, board_name, n_subdevices");
> + seq_puts(m,
> + "comedi version " COMEDI_RELEASE "\n"
> + "format string: %s\n",
> + "\"%2d: %-20s %-20s %4d\", i, "
> + "driver_name, board_name, n_subdevices");
Please compile the files patched by your patches
before submitting the patches.
This doesn't compile, the seq_printf is correct
and the recommendation to use seq_puts not correct.
checkpatch ain't perfect.
> @@ -57,10 +57,11 @@ static int comedi_read(struct seq_file *m, void *v)
>
> for (driv = comedi_drivers; driv; driv = driv->next) {
> seq_printf(m, "%s:\n", driv->driver_name);
> - for (i = 0; i < driv->num_names; i++)
> + for (i = 0; i < driv->num_names; i++) {
> seq_printf(m, " %s\n",
> *(char **)((char *)driv->board_name +
> i * driv->offset));
> + }
Adding braces here is not necessary.
Run checkpatch on your patches too.
next prev parent reply other threads:[~2013-06-07 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 7:27 Daniel Hamacher
2013-06-07 7:47 ` Joe Perches [this message]
2013-06-07 7:36 Daniel Hamacher
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=1370591253.2209.99.camel@joe-AO722 \
--to=joe@perches.com \
--cc=abotti@mev.co.uk \
--cc=danielhamacher.dh@gmail.com \
--cc=fmhess@users.sourceforge.net \
--cc=greg@kroah.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
all inboxes | Powered by JetHome®