From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Michal Simek <monstr@monstr.eu>
Cc: "Sören Brinkmann" <soren.brinkmann@xilinx.com>,
"Michal Simek" <michal.simek@xilinx.com>,
"Josh Cartwright" <joshc@eso.teric.us>,
"Mike Turquette" <mturquette@linaro.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Peter Crosthwaite" <peter.crosthwaite@xilinx.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Arnd Bergmann" <arnd@arndb.de>,
"Russell King" <linux@arm.linux.org.uk>,
"Stephen Warren" <swarren@wwwdotorg.org>,
"Jiri Slaby" <jslaby@suse.cz>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH 1/7] tty: xuartps: Sort #includes alphabetically
Date: Wed, 1 May 2013 06:30:16 -0700 [thread overview]
Message-ID: <20130501133016.GA2977@kroah.com> (raw)
In-Reply-To: <5180BB21.2080306@monstr.eu>
On Wed, May 01, 2013 at 08:50:09AM +0200, Michal Simek wrote:
> On 05/01/2013 02:23 AM, Greg Kroah-Hartman wrote:
> > On Tue, Apr 30, 2013 at 05:05:40PM -0700, Sören Brinkmann wrote:
> >> On Tue, Apr 30, 2013 at 05:00:48PM -0700, Greg Kroah-Hartman wrote:
> >>> On Tue, Apr 30, 2013 at 04:57:58PM -0700, Soren Brinkmann wrote:
> >>>> Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com>
> >>>> CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >>>> CC: Jiri Slaby <jslaby@suse.cz>
> >>>> CC: linux-serial@vger.kernel.org
> >>>
> >>> Why would you need/want to do this?
> >> I often come across duplicated includes. Having some kind of order helps
> >> avoiding that, imho.
> >
> > We have a tool to handle duplicated includes, no need to put them in
> > sorted order for them to be detected.
>
> What's the name of tool which does that?
> I have seen results from it but have never tried to find it out name and
> how to use it.
scripts/checkincludes.pl
next prev parent reply other threads:[~2013-05-01 13:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 23:57 [PATCH 0/7] Zynq: revised CCF code Soren Brinkmann
2013-04-30 23:57 ` [PATCH 1/7] tty: xuartps: Sort #includes alphabetically Soren Brinkmann
2013-05-01 0:00 ` Greg Kroah-Hartman
2013-05-01 0:05 ` Sören Brinkmann
2013-05-01 0:23 ` Greg Kroah-Hartman
2013-05-01 6:50 ` Michal Simek
2013-05-01 13:30 ` Greg Kroah-Hartman [this message]
2013-05-01 15:39 ` Sören Brinkmann
2013-04-30 23:57 ` [PATCH 2/7] tty: xuartps: Remove suspend/resume functions Soren Brinkmann
2013-04-30 23:58 ` [PATCH 3/7] clocksource/cadence_ttc: Sort #includes alphabetically Soren Brinkmann
2013-04-30 23:58 ` [PATCH 4/7] clk: zynq: Factor out PLL driver Soren Brinkmann
2013-04-30 23:58 ` [PATCH 5/7] clk: zynq: Add clock controller driver Soren Brinkmann
2013-04-30 23:58 ` [PATCH 6/7] arm: zynq: Migrate platform to clock controller Soren Brinkmann
2013-04-30 23:58 ` [PATCH 7/7] clk: zynq: Remove deprecated clock code Soren Brinkmann
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=20130501133016.GA2977@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=joshc@eso.teric.us \
--cc=jslaby@suse.cz \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=mturquette@linaro.org \
--cc=peter.crosthwaite@xilinx.com \
--cc=soren.brinkmann@xilinx.com \
--cc=swarren@wwwdotorg.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