public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/4] ARM: dts: sun7i: Add lradc node
Date: Wed, 22 Oct 2014 10:38:02 +0200	[thread overview]
Message-ID: <20141022083802.GE7893@lukather> (raw)
In-Reply-To: <1413879890-7254-5-git-send-email-hdegoede@redhat.com>

Hi Hans,

On Tue, Oct 21, 2014 at 10:24:50AM +0200, Hans de Goede wrote:
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
>  arch/arm/boot/dts/sun7i-a20-olinuxino-micro.dts | 48 +++++++++++++++++++++++++
>  arch/arm/boot/dts/sun7i-a20.dtsi                |  7 ++++
>  2 files changed, 55 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/sun7i-a20-olinuxino-micro.dts b/arch/arm/boot/dts/sun7i-a20-olinuxino-micro.dts
> index 9d669cdf..85e7194 100644
> --- a/arch/arm/boot/dts/sun7i-a20-olinuxino-micro.dts
> +++ b/arch/arm/boot/dts/sun7i-a20-olinuxino-micro.dts
> @@ -14,6 +14,7 @@
>  /dts-v1/;
>  /include/ "sun7i-a20.dtsi"
>  /include/ "sunxi-common-regulators.dtsi"
> +#include <dt-bindings/input/input.h>

I'm just wondering... Weren't we supposed to switch all includes to
the preprocessor syntax in such a case?

Maybe to handle the case were the DTSIs would have to use some
preprocessors macros that wouldn't be expanded in this case?

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141022/de46738a/attachment.sig>

  reply	other threads:[~2014-10-22  8:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21  8:24 [PATCH v2 0/4] input: Add new sun4i-lradc-keys driver Hans de Goede
2014-10-21  8:24 ` [PATCH v2 1/4] " Hans de Goede
2014-10-21 17:04   ` Maxime Ripard
2014-10-22 10:45     ` Hans de Goede
2014-10-21  8:24 ` [PATCH v2 2/4] ARM: dts: sun4i: Add lradc node Hans de Goede
2014-10-21  8:24 ` [PATCH v2 3/4] ARM: dts: sun5i: " Hans de Goede
2014-10-21 16:21   ` Dmitry Torokhov
2014-10-21 20:29     ` Hans de Goede
2014-10-22 10:42       ` [linux-sunxi] " Hans de Goede
2014-10-21  8:24 ` [PATCH v2 4/4] ARM: dts: sun7i: " Hans de Goede
2014-10-22  8:38   ` Maxime Ripard [this message]
2014-10-22  8:46     ` [linux-sunxi] " Hans de Goede
  -- strict thread matches above, loose matches on Subject: below --
2014-01-02  9:58 [PATCH v2 0/4] input: Add new sun4i-lradc-keys driver Hans de Goede
2014-01-02  9:58 ` [PATCH v2 4/4] ARM: dts: sun7i: Add lradc node Hans de Goede

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=20141022083802.GE7893@lukather \
    --to=maxime.ripard@free-electrons.com \
    --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