From: Ian Abbott <abbotti@mev.co.uk>
To: Geliang Tang <geliangtang@163.com>,
hsweeten@visionengravers.com, gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: comedi: fix coding style issues
Date: Mon, 18 May 2015 12:37:09 +0100 [thread overview]
Message-ID: <5559CEE5.8040102@mev.co.uk> (raw)
In-Reply-To: <1431749763-2378-1-git-send-email-geliangtang@163.com>
On 16/05/15 05:16, Geliang Tang wrote:
> 1) Fixed an error found by checkpatch.pl.
> ERROR: space required after that ',' (ctx:VxV)
> ./drivers/ni_mio_common.c:3764
> 2) Changed "register 0x%x" to "register=0x%x" to keep the consistency
> of this file.
> 3) The kernel version is next-20150515, 4.1.0-rc3.
You shouldn't mention point 3 in the commit message as it will look a
bit strange when it ends up in the commit log. If you need to mention
that, it should go after the commit message, separated from the patch by
a "---" line like this:
Body of commit message goes here.
Signed off by and Cc lines go here.
---
Additional patch commentary goes here.
---
Actual patch goes here.
Git will ignore the additional commentary when the patch is applied.
>
> Signed-off-by: Geliang Tang <geliangtang@163.com>
> ---
> drivers/staging/comedi/drivers/ni_mio_common.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/comedi/drivers/ni_mio_common.c b/drivers/staging/comedi/drivers/ni_mio_common.c
> index 9dfd4e6..6cc304a 100644
> --- a/drivers/staging/comedi/drivers/ni_mio_common.c
> +++ b/drivers/staging/comedi/drivers/ni_mio_common.c
> @@ -3761,7 +3761,7 @@ static unsigned int ni_gpct_to_stc_register(struct comedi_device *dev,
> if (reg < ARRAY_SIZE(ni_gpct_to_stc_regmap)) {
> regmap = &ni_gpct_to_stc_regmap[reg];
> } else {
> - dev_warn(dev->class_dev,"%s: unhandled register 0x%x\n",
> + dev_warn(dev->class_dev, "%s: unhandled register=0x%x\n",
> __func__, reg);
> return 0;
> }
>
Apart from that niggle, the patch looks good!
Reviewed-by: Ian Abbott <abbotti@mev.co.uk>
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Web: http://www.mev.co.uk/ )=-
next prev parent reply other threads:[~2015-05-18 11:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-16 4:16 Geliang Tang
2015-05-18 11:37 ` Ian Abbott [this message]
2015-05-20 14:54 ` [PATCH v2] " Geliang Tang
2015-05-24 20:11 ` Greg KH
2015-05-25 14:20 ` [PATCH v3 0/2] " Geliang Tang
2015-05-25 14:20 ` [PATCH v3 1/2] staging: comedi: fix checkpatch error Geliang Tang
2015-05-25 14:20 ` [PATCH v3 2/2] staging: comedi: keep the consistency Geliang Tang
2015-09-18 16:52 [PATCH] Staging: comedi: Fix coding style issues Punit Vara
2015-09-19 2:43 ` Greg KH
2015-09-19 16:27 ` punit vara
2015-09-19 16:37 ` Greg KH
2015-09-19 17:51 ` punit vara
2015-09-19 18:13 ` punit vara
2015-09-20 1:20 ` Jaime Arrocha
2015-09-20 8:29 ` punit vara
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=5559CEE5.8040102@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=geliangtang@163.com \
--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
Powered by JetHome