From: Joe Perches <joe@perches.com>
To: Camille Begue <camille.begue44@gmail.com>
Cc: devel@driverdev.osuosl.org, Ian Abbott <abbotti@mev.co.uk>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] staging: comedi: Fix checkpatch warning
Date: Fri, 04 Apr 2014 12:56:15 -0700 [thread overview]
Message-ID: <1396641375.2863.18.camel@joe-AO722> (raw)
In-Reply-To: <1396638941-16099-1-git-send-email-camille.begue44@gmail.com>
On Fri, 2014-04-04 at 21:15 +0200, Camille Begue wrote:
> This patch is part of eudyptula challenge
Hello Camille.
Please do not write commit log messages like this.
Say what's wrong with the code, not why you did it.
Write something like:
Wrap lines > 80 columns.
> diff --git a/drivers/staging/comedi/comedi_fops.c b/drivers/staging/comedi/comedi_fops.c
[]
> @@ -1435,13 +1435,16 @@ static int __comedi_get_user_cmd(struct comedi_device *dev,
> s = &dev->subdevices[cmd->subdev];
>
> if (s->type == COMEDI_SUBD_UNUSED) {
> - dev_dbg(dev->class_dev, "%d not valid subdevice\n", cmd->subdev);
> + dev_dbg(dev->class_dev,
> + "%d not valid subdevice\n",
> + cmd->subdev);
If you really want to fix > 80 column lines, it'd be
better to keep the dev_dbg and format on the same line
1 2 3 4 5 6 7 8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
dev_dbg(dev->class_dev, "%d not valid subdevice\n",
cmd->subdev);
> return -EIO;
> }
>
> if (!s->do_cmd || !s->do_cmdtest || !s->async) {
> dev_dbg(dev->class_dev,
> - "subdevice %d does not support commands\n", cmd->subdev);
> + "subdevice %d does not support commands\n",
> + cmd->subdev);
> return -EIO;
> }
>
here too
next prev parent reply other threads:[~2014-04-04 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 19:15 [PATCH 1/1] staging: comedi: Fix checkpatch warning Camille Begue
2014-04-04 19:56 ` Joe Perches [this message]
2014-04-04 21:24 ` 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=1396641375.2863.18.camel@joe-AO722 \
--to=joe@perches.com \
--cc=abbotti@mev.co.uk \
--cc=camille.begue44@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.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