From: monstr@monstr.eu (Michal Simek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/7] tty: xuartps: Sort #includes alphabetically
Date: Wed, 01 May 2013 08:50:09 +0200 [thread overview]
Message-ID: <5180BB21.2080306@monstr.eu> (raw)
In-Reply-To: <20130501002321.GB7435@kroah.com>
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 at 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.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130501/58277851/attachment.sig>
next prev parent reply other threads:[~2013-05-01 6:50 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 [this message]
2013-05-01 13:30 ` Greg Kroah-Hartman
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=5180BB21.2080306@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-arm-kernel@lists.infradead.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).