[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171128134012.GA18424@kroah.com>
Date: Tue, 28 Nov 2017 14:40:12 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Benjamin Gaignard <benjamin.gaignard@...aro.org>
Cc: Laura Abbott <labbott@...hat.com>,
Sumit Semwal <sumit.semwal@...aro.org>,
Arve Hjønnevåg <arve@...roid.com>,
Riley Andrews <riandrews@...roid.com>,
Mark Brown <broonie@...nel.org>,
Dan Carpenter <dan.carpenter@...cle.com>,
driverdevel <devel@...verdev.osuosl.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
linux-api@...r.kernel.org
Subject: Re: [PATCH v6 1/2] staging: ion: reorder include
On Tue, Nov 28, 2017 at 02:34:00PM +0100, Benjamin Gaignard wrote:
> 2017-11-28 14:20 GMT+01:00 Greg KH <gregkh@...uxfoundation.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
Powered by blists - more mailing lists