From: Greg KH <gregkh@linuxfoundation.org>
To: ChinmayVS <cvs268@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uio: uio_cif: Fix style issues
Date: Sat, 3 Dec 2016 18:15:15 +0100 [thread overview]
Message-ID: <20161203171515.GC5277@kroah.com> (raw)
In-Reply-To: <1480774184-4655-1-git-send-email-cvs268@gmail.com>
On Sat, Dec 03, 2016 at 07:39:44PM +0530, ChinmayVS wrote:
> - Update header-file inclusion path.
> - Fix indentation of switch and case.
> - Remove extra space in function calls.
>
> Signed-off-by: ChinmayVS <cvs268@gmail.com>
I need a "real" name here, one that you use on legal documents.
Also, please break this up into tiny individual patches, one doing each
thing.
And finally, please work in the drivers/staging/ portion of the kernel
if you wish to do cleanup patches like this, that will give you the
experience to not mess up on patches for the "core" kernel like this.
good luck!
greg k-h
prev parent reply other threads:[~2016-12-03 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 14:09 [PATCH] uio: uio_cif: Fix style issues ChinmayVS
2016-12-03 17:15 ` 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=20161203171515.GC5277@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cvs268@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;
as well as URLs for NNTP newsgroup(s).