From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Neil Singh <neil2468@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Florian Schilhabel <florian.c.schilhabel@googlemail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
driverdev-devel@linuxdriverproject.org
Subject: Re: [PATCH] staging: rtl8712: Cleanup codestyle
Date: Wed, 6 Dec 2017 12:15:40 +0100 [thread overview]
Message-ID: <20171206111540.GA29482@kroah.com> (raw)
In-Reply-To: <20171206103138.GA7701@red>
On Wed, Dec 06, 2017 at 05:31:38PM +0700, Neil Singh wrote:
> Fix following checkpatch.pl messages:
>
> WARNING: line over 80 characters
> 1000: FILE: rtl871x_security.c:1000:
>
> ERROR: code indent should use tabs where possible
> 1408: FILE: rtl871x_security.c:1408:
>
> WARNING: please, no spaces at the start of a line
> 1408: FILE: rtl871x_security.c:1408:
That's multiple things, so this should be multiple patches...
thanks,
greg k-h
prev parent reply other threads:[~2017-12-06 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 10:31 [PATCH] staging: rtl8712: Cleanup codestyle Neil Singh
2017-12-06 11:15 ` Greg Kroah-Hartman [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=20171206111540.GA29482@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=florian.c.schilhabel@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neil2468@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