From: Greg KH <gregkh@linuxfoundation.org>
To: Benjamin Gaignard <benjamin.gaignard@linaro.org>
Cc: "Laura Abbott" <labbott@redhat.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Riley Andrews" <riandrews@android.com>,
"Mark Brown" <broonie@kernel.org>,
"Dan Carpenter" <dan.carpenter@oracle.com>,
driverdevel <devel@driverdev.osuosl.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
linux-api@vger.kernel.org
Subject: Re: [PATCH v6 1/2] staging: ion: reorder include
Date: Tue, 28 Nov 2017 14:40:12 +0100 [thread overview]
Message-ID: <20171128134012.GA18424@kroah.com> (raw)
In-Reply-To: <CA+M3ks7v32iozDrj0HZ4RJLiokffnZyyZNUezg+ExD9=rdSLQg@mail.gmail.com>
On Tue, Nov 28, 2017 at 02:34:00PM +0100, Benjamin Gaignard wrote:
> 2017-11-28 14:20 GMT+01:00 Greg KH <gregkh@linuxfoundation.org>:
> > On Mon, Nov 06, 2017 at 04:59:44PM +0100, Benjamin Gaignard wrote:
> >> Put include in alphabetic order
> >
> > Why???
>
> Mainly because the next patch in the series adds new includes and I have
> decide to split clean-up and new feature patches
That's fine, but this really isn't needed for any type of "clean-up" at
all. But oh well, if you all like it that way, I'm not going to
complain that much :)
greg k-h
next prev parent reply other threads:[~2017-11-28 13:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 15:59 [PATCH v6 0/2] staging: ion: get one device per heap Benjamin Gaignard
2017-11-06 15:59 ` [PATCH v6 1/2] staging: ion: reorder include Benjamin Gaignard
2017-11-09 21:02 ` Laura Abbott
2017-11-28 13:20 ` Greg KH
2017-11-28 13:34 ` Benjamin Gaignard
2017-11-28 13:40 ` Greg KH [this message]
2017-11-06 15:59 ` [PATCH v6 2/2] staging: ion: create one device entry per heap Benjamin Gaignard
2017-11-09 21:17 ` Laura Abbott
2017-11-27 10:46 ` Benjamin Gaignard
2017-11-27 11:43 ` Greg Kroah-Hartman
2017-11-27 16:12 ` Daniel Vetter
2017-11-27 16:30 ` Mark Brown
2017-11-28 13:32 ` Greg KH
2017-11-28 16:26 ` Mark Brown
2017-11-28 17:08 ` Greg KH
2017-11-28 17:12 ` Mark Brown
2017-11-28 17:28 ` Greg KH
2017-11-28 17:37 ` Mark Brown
2017-11-28 18:00 ` Greg KH
2017-11-29 14:00 ` Benjamin Gaignard
2017-12-02 15:53 ` Greg KH
2017-12-05 23:01 ` Laura Abbott
2017-12-06 6:28 ` 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=20171128134012.GA18424@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=benjamin.gaignard@linaro.org \
--cc=broonie@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=labbott@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.com \
--cc=sumit.semwal@linaro.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).