From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: csmanjuvijay@gmail.com
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] USB: EHCI: spear: fix code warnings
Date: Sat, 10 Dec 2016 15:07:41 +0100 [thread overview]
Message-ID: <20161210140741.GA19434@kroah.com> (raw)
In-Reply-To: <1481236811-10462-1-git-send-email-csmanjuvijay@gmail.com>
On Thu, Dec 08, 2016 at 10:40:11PM +0000, csmanjuvijay@gmail.com wrote:
> From: Manjunath Goudar <csmanjuvijay@gmail.com>
>
> This patch will fix the checkpatch.pl following warnings
> WARNING: Block comments should align the * on each line
> WARNING: space prohibited before semicolon
I've said this before, only do one "type" of fix per patch, and not "fix
all coding style issues".
The subject is also a bit "harsh" there is not "code warnings", that
normally means a build warning. These are just minor coding _style_
warnings.
So please break up all of your patches like this and resend them as a
single series of patches. I'll drop all of your pending ones from my
queue right now.
thanks,
greg k-h
parent reply other threads:[~2016-12-10 14:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1481236811-10462-1-git-send-email-csmanjuvijay@gmail.com>]
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=20161210140741.GA19434@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=csmanjuvijay@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.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