From: Greg KH <gregkh@linuxfoundation.org>
To: jitendra kumar khasdev <jkhasdev@gmail.com>
Cc: abbotti@mev.co.uk, hsweeten@visionengravers.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7] Staging: comedi: patch to fix line over 80 characters warning
Date: Sat, 17 Jan 2015 14:33:12 -0800 [thread overview]
Message-ID: <20150117223312.GA15083@kroah.com> (raw)
In-Reply-To: <1420865403-4932-1-git-send-email-jkhasdev@gmail.com>
On Sat, Jan 10, 2015 at 10:20:03AM +0530, jitendra kumar khasdev wrote:
> This is patch to pcl812.c that fix line over 80 characters warning
> which is found by checkpatch.pl tool. Reduce the extra space around
> equal sign that fix warning.
>
> Signed-off-by: Jitendra kumar khasdev <jkhasdev@gmail.com>
> ---
> drivers/staging/comedi/drivers/pcl812.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Does not apply to my tree :(
next prev parent reply other threads:[~2015-01-17 23:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 4:50 [PATCH v7] Staging: comedi: patch to fix line over 80 characters warning jitendra kumar khasdev
2015-01-17 22:33 ` Greg KH [this message]
2015-01-18 14:17 ` jitendra kumar khasdev
2015-01-18 22:50 ` Greg KH
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=20150117223312.GA15083@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox