From: Ian Abbott <abbotti@mev.co.uk>
To: jitendra kumar khasdev <jkhasdev@gmail.com>,
hsweeten@visionengravers.com, gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] Staging: comedi: fix line over 80 characters warning
Date: Mon, 26 Jan 2015 11:19:02 +0000 [thread overview]
Message-ID: <54C622A6.80300@mev.co.uk> (raw)
In-Reply-To: <1422040280-20213-2-git-send-email-jkhasdev@gmail.com>
On 23/01/15 19:11, jitendra kumar khasdev wrote:
> This is patch to file jr3_pci.h that fix up warning line
> over 80 character which is found by checkpatch tool.
>
> Signed-off-by: Jitendra Kumar Khasdev <jkhasdev@gmail.com>
> ---
> drivers/staging/comedi/drivers/jr3_pci.h | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/comedi/drivers/jr3_pci.h b/drivers/staging/comedi/drivers/jr3_pci.h
> index 20478ae..356811d 100644
> --- a/drivers/staging/comedi/drivers/jr3_pci.h
> +++ b/drivers/staging/comedi/drivers/jr3_pci.h
> @@ -261,8 +261,9 @@ struct intern_transform {
> } link[8];
> };
>
> -/* JR3 force/torque sensor data definition. For more information see sensor and */
> -/* hardware manuals. */
> +/* JR3 force/torque sensor data definition. For more information see sensor
> + * and hardware manuals.
> + */
The usual block comment style is like this:
/*
* Blah blah
* blah.
*/
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Web: http://www.mev.co.uk/ )=-
next prev parent reply other threads:[~2015-01-26 11:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 19:11 [PATCH v1 0/2] line over 80 character warnings jitendra kumar khasdev
2015-01-23 19:11 ` [PATCH v1 1/2] Staging: comedi: fix line over 80 characters warning jitendra kumar khasdev
2015-01-26 11:19 ` Ian Abbott [this message]
2015-01-23 19:11 ` [PATCH v1 2/2] " jitendra kumar khasdev
2015-01-24 2:29 ` Greg KH
2015-01-26 11:20 ` Ian Abbott
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=54C622A6.80300@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=jkhasdev@gmail.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 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.