From: Ian Abbott <abbotti@mev.co.uk>
To: Ravishankar Karkala Mallikarjunayya <ravishankarkm32@gmail.com>,
hsweeten@visionengravers.com, gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] Staging: comedi: fix line over 80 characters issue in s626.c
Date: Fri, 20 May 2016 11:15:07 +0100 [thread overview]
Message-ID: <573EE3AB.4010307@mev.co.uk> (raw)
In-Reply-To: <1463725362-13784-1-git-send-email-ravishankarkm32@gmail.com>
On 20/05/16 07:22, Ravishankar Karkala Mallikarjunayya wrote:
> This is a patch to the s626.c file that fixes up a line over
> 80 characters issues found by the checkpatch.pl tool.
>
> Signed-off-by: Ravishankar Karkala Mallikarjunayya <ravishankarkm32@gmail.com>
> ---
> Changes since V1:
> - No change
> ---
> drivers/staging/comedi/drivers/s626.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Thanks!
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:[~2016-05-20 10:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 6:22 [PATCH v2 4/4] Staging: comedi: fix line over 80 characters issue in s626.c Ravishankar Karkala Mallikarjunayya
2016-05-20 10:15 ` Ian Abbott [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-28 5:26 [PATCH v2 1/4] staging : comedi : fix type issues " Ravishankar Karkala Mallikarjunayya
2016-05-28 5:26 ` [PATCH v2 4/4] Staging: comedi: fix line over 80 characters issue " Ravishankar Karkala Mallikarjunayya
2016-05-30 14:21 ` Luis de Bethencourt
2016-06-18 3:51 ` Greg KH
2016-06-18 14:21 ` Luis de Bethencourt
2016-05-31 10:31 ` 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=573EE3AB.4010307@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ravishankarkm32@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.