From: Greg KH <gregkh@linuxfoundation.org>
To: Ravishankar Karkala Mallikarjunayya <ravishankarkm32@gmail.com>
Cc: abbotti@mev.co.uk, hsweeten@visionengravers.com,
geliangtang@163.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] Staging: comedi: fix WARNING issue in s626.c
Date: Thu, 10 Mar 2016 19:32:51 -0800 [thread overview]
Message-ID: <20160311033251.GA31261@kroah.com> (raw)
In-Reply-To: <1457592730-14347-2-git-send-email-ravishankarkm32@gmail.com>
On Thu, Mar 10, 2016 at 12:22:07PM +0530, Ravishankar Karkala Mallikarjunayya wrote:
> This is a patch to the s626.c file that fixes up a Block comments issues
> found by the checkpatch.pl tool.
>
> i.e. Block comments use a trailing */ on a separate line
>
> Signed-off-by: Ravishankar Karkala Mallikarjunayya <ravishankarkm32@gmail.com>
> Reviewed-by: Ian Abbott <abbotti@mev.co.uk>
> ---
> drivers/staging/comedi/drivers/s626.c | 38 ++++++++++++++++++++++-------------
> 1 file changed, 24 insertions(+), 14 deletions(-)
You have two subjects that are identical in this series, which isn't
allowed, please fix up and make them unique.
next prev parent reply other threads:[~2016-03-11 3:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 6:52 [PATCH 1/5] Staging: comedi: fix type issue in s626.c Ravishankar Karkala Mallikarjunayya
2016-03-10 6:52 ` [PATCH 2/5] Staging: comedi: fix WARNING " Ravishankar Karkala Mallikarjunayya
2016-03-10 10:42 ` Ian Abbott
2016-03-11 3:32 ` Greg KH [this message]
2016-03-10 6:52 ` [PATCH 3/5] " Ravishankar Karkala Mallikarjunayya
2016-03-10 10:42 ` Ian Abbott
2016-03-10 6:52 ` [PATCH 4/5] Staging: comedi: fix CHECK issue in ni_tio.c Ravishankar Karkala Mallikarjunayya
2016-03-10 10:42 ` Ian Abbott
2016-03-10 6:52 ` [PATCH 5/5] Staging: comedi: fix type " Ravishankar Karkala Mallikarjunayya
2016-03-10 10:42 ` Ian Abbott
2016-03-10 10:41 ` [PATCH 1/5] Staging: comedi: fix type issue in s626.c Ian Abbott
2016-03-11 3:32 ` 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=20160311033251.GA31261@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=geliangtang@163.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).