From: Greg KH <gregkh@linuxfoundation.org>
To: Dhanunjaya <dhanunjaya.matrix@gmail.com>
Cc: abbotti@mev.co.uk, hsweeten@visionengravers.com,
wfp5p@virginia.edu, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: comedi: fix semicolon coding style issue in ni_660x.c
Date: Wed, 16 Oct 2013 12:38:56 -0700 [thread overview]
Message-ID: <20131016193856.GA3913@kroah.com> (raw)
In-Reply-To: <1381927094-13457-1-git-send-email-dhanunjaya.matrix@gmail.com>
On Wed, Oct 16, 2013 at 06:08:14PM +0530, Dhanunjaya wrote:
> This is a patch to the ni_660x.c file that fixes up a semicolon warning
> found by the checkpatch.pl tool
> ---
No signed-off-by: so I can't take this patch, sorry.
greg k-h
prev parent reply other threads:[~2013-10-16 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 12:38 [PATCH] Staging: comedi: fix semicolon coding style issue in ni_660x.c Dhanunjaya
2013-10-16 14:07 ` Ian Abbott
2013-10-16 19:38 ` Greg KH [this message]
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=20131016193856.GA3913@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=dhanunjaya.matrix@gmail.com \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wfp5p@virginia.edu \
/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