From: Jonathan Cameron <jic23@kernel.org>
To: Gregory CLEMENT <gregory.clement@bootlin.com>
Cc: devicetree@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-iio@vger.kernel.org, Hartmut Knaack <knaack.h@gmx.de>,
Vladimir Zapolskiy <vz@mleia.com>,
Rob Herring <robh+dt@kernel.org>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Sylvain Lemieux <slemieux.tyco@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/4] iio: adc: lpc32xx: Sort headers
Date: Sat, 16 Mar 2019 17:17:47 +0000 [thread overview]
Message-ID: <20190316171747.34be37ab@archlinux> (raw)
In-Reply-To: <20190315095231.17001-2-gregory.clement@bootlin.com>
On Fri, 15 Mar 2019 10:52:28 +0100
Gregory CLEMENT <gregory.clement@bootlin.com> wrote:
> Sort the headers in alphabetic order in order to ease the maintenance for
> this part.
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
Applied,
Thanks,
Jonathan
> ---
> drivers/iio/adc/lpc32xx_adc.c | 19 +++++++++----------
> 1 file changed, 9 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/iio/adc/lpc32xx_adc.c b/drivers/iio/adc/lpc32xx_adc.c
> index e361c1532a75..7084f804504e 100644
> --- a/drivers/iio/adc/lpc32xx_adc.c
> +++ b/drivers/iio/adc/lpc32xx_adc.c
> @@ -7,20 +7,19 @@
> * Copyright (C) 2011, 2012 Roland Stigge <stigge@antcom.de>
> */
>
> -#include <linux/module.h>
> -#include <linux/platform_device.h>
> -#include <linux/interrupt.h>
> -#include <linux/device.h>
> -#include <linux/kernel.h>
> -#include <linux/slab.h>
> -#include <linux/io.h>
> #include <linux/clk.h>
> -#include <linux/err.h>
> #include <linux/completion.h>
> -#include <linux/of.h>
> -
> +#include <linux/device.h>
> +#include <linux/err.h>
> #include <linux/iio/iio.h>
> #include <linux/iio/sysfs.h>
> +#include <linux/interrupt.h>
> +#include <linux/io.h>
> +#include <linux/kernel.h>
> +#include <linux/module.h>
> +#include <linux/of.h>
> +#include <linux/platform_device.h>
> +#include <linux/slab.h>
>
> /*
> * LPC32XX registers definitions
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-16 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 9:52 [PATCH v2 0/4] Adding scale support to the lpc32xx ADC driver Gregory CLEMENT
2019-03-15 9:52 ` [PATCH v2 1/4] iio: adc: lpc32xx: Sort headers Gregory CLEMENT
2019-03-16 17:17 ` Jonathan Cameron [this message]
2019-03-15 9:52 ` [PATCH v2 2/4] iio: adc: lpc32xx: Cleanup headers Gregory CLEMENT
2019-03-16 17:23 ` Jonathan Cameron
2019-03-15 9:52 ` [PATCH v2 3/4] iio: adc: lpc32xx: Add scale feature Gregory CLEMENT
2019-03-16 17:26 ` Jonathan Cameron
2019-03-15 9:52 ` [PATCH v2 4/4] dt-bindings: iio: adc: lpc32xx-adc: Document vref-supply Gregory CLEMENT
2019-03-16 17:27 ` Jonathan Cameron
2019-03-16 17:16 ` [PATCH v2 0/4] Adding scale support to the lpc32xx ADC driver Jonathan Cameron
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=20190316171747.34be37ab@archlinux \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=slemieux.tyco@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vz@mleia.com \
/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).