public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Gabriel FERNANDEZ <gabriel.fernandez@st.com>,
	Srinivas Kandagatla <srinivas.kandagatla@gmail.com>,
	Maxime Coquelin <maxime.coquelin@st.com>,
	Patrice Chotard <patrice.chotard@st.com>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Russell King <linux@arm.linux.org.uk>
Cc: devicetree@vger.kernel.org, kernel@stlinux.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Lee Jones <lee.jones@linaro.org>,
	Gabriel Fernandez <gabriel.fernandez@linaro.org>
Subject: Re: [PATCH 0/4] Enable ST Keyscan driver
Date: Tue, 06 May 2014 13:39:34 +0100	[thread overview]
Message-ID: <5368D806.8050609@linaro.org> (raw)
In-Reply-To: <1399304320-18197-1-git-send-email-gabriel.fernandez@linaro.org>

All the DT patches look good for me.
Acked-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>

I think It will be better to send a pull request to Arnd/Olof including 
other reviewed DT patches.

thanks,
srini


On 05/05/14 16:38, Gabriel FERNANDEZ wrote:
> The goal of this series is to enable ST Keyscan support to ST SoCs.
> The DT definition is added for STiH415 and STiH416 SoCs on
> B2000 board.
> Tested on B2000 sti board.
>
> Gabriel Fernandez (4):
>    ARM: STi: DT: add keyscan for stih415
>    ARM: STi: DT: add keyscan for stih416
>    ARM: STi: DT: add keyscan for stih41x-b2000
>    ARM: multi_v7_defconfig: add ST Keyscan driver
>
>   arch/arm/boot/dts/stih415-pinctrl.dtsi | 16 ++++++++++++++++
>   arch/arm/boot/dts/stih415.dtsi         | 12 ++++++++++++
>   arch/arm/boot/dts/stih416-pinctrl.dtsi | 16 ++++++++++++++++
>   arch/arm/boot/dts/stih416.dtsi         | 12 ++++++++++++
>   arch/arm/boot/dts/stih41x-b2000.dtsi   | 23 +++++++++++++++++++++++
>   arch/arm/configs/multi_v7_defconfig    |  1 +
>   6 files changed, 80 insertions(+)
>

  parent reply	other threads:[~2014-05-06 12:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 15:38 [PATCH 0/4] Enable ST Keyscan driver Gabriel FERNANDEZ
2014-05-05 15:38 ` [PATCH 1/4] ARM: STi: DT: add keyscan for stih415 Gabriel FERNANDEZ
2014-05-05 15:38 ` [PATCH 2/4] ARM: STi: DT: add keyscan for stih416 Gabriel FERNANDEZ
2014-05-05 15:38 ` [PATCH 3/4] ARM: STi: DT: add keyscan for stih41x-b2000 Gabriel FERNANDEZ
2014-05-05 15:38 ` [PATCH 4/4] ARM: multi_v7_defconfig: add ST Keyscan driver Gabriel FERNANDEZ
2014-05-06 12:39 ` Srinivas Kandagatla [this message]
2014-05-06 15:48   ` [PATCH 0/4] Enable " Maxime Coquelin

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=5368D806.8050609@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gabriel.fernandez@linaro.org \
    --cc=gabriel.fernandez@st.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=kernel@stlinux.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=maxime.coquelin@st.com \
    --cc=patrice.chotard@st.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=srinivas.kandagatla@gmail.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