From: Greg KH <greg@kroah.com>
To: Sorin Facaoaru <work@sorin.cc>
Cc: ccross@android.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: android: ion: fix coding style
Date: Sun, 14 Sep 2014 09:50:18 -0700 [thread overview]
Message-ID: <20140914165018.GA2821@kroah.com> (raw)
In-Reply-To: <1410651970-3837-1-git-send-email-work@sorin.cc>
First off, thanks for the patches.
But, they need some tweaks before I can accept them.
You sent a bunch of patches, all with the same exact subject, with no
hint of which order they should be applied in, or what exactly they do.
On Sat, Sep 13, 2014 at 04:46:10PM -0700, Sorin Facaoaru wrote:
> - add line after declaration
> - remove return statement in empty void function
For this patch, you are doing two different things, in the same file,
that should be two different patches. But you might be able to merge
them with your other patches.
Make your patches do "just one thing" from a logical point of view.
For example, you could have a patch titled:
[PATCH 01/05] staging: android: ion: remove unneeded returns
that just removed the unneeded return statemnents for all of the ion
files.
Then 4 other patches that do 4 other "logical" things, telling me what
order to apply them in.
Can you please fix up all of your recent submissions and resend in that
format?
> Signed-off-by: Sorin Facaoaru <work@sorin.cc>
You have trailing whitespace here :(
thanks,
greg k-h
next prev parent reply other threads:[~2014-09-14 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 23:46 [PATCH] Staging: android: ion: fix coding style Sorin Facaoaru
2014-09-14 16:50 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-14 0:07 Sorin Facaoaru
2014-09-14 0:09 Sorin Facaoaru
2014-09-14 0:11 Sorin Facaoaru
2014-09-14 0:13 Sorin Facaoaru
2014-09-14 0:19 Sorin Facaoaru
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=20140914165018.GA2821@kroah.com \
--to=greg@kroah.com \
--cc=ccross@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=work@sorin.cc \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.