From: Lokesh Vutla <lokeshvutla@ti.com>
To: Keerthy <j-keerthy@ti.com>, <linux-patch-review@list.ti.com>
Cc: <nm@ti.com>, <mark.rutland@arm.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<tony@atomide.com>, <galak@codeaurora.org>
Subject: Re: [PATCH 0/2] ARM: dts: dra72-evm: Add i2c1 and tps65917 nodes
Date: Mon, 28 Jul 2014 12:00:57 +0530 [thread overview]
Message-ID: <53D5EE21.1040000@ti.com> (raw)
In-Reply-To: <1406528334-4415-1-git-send-email-j-keerthy@ti.com>
On Monday 28 July 2014 11:48 AM, Keerthy wrote:
> The patch series adds i2c1 and tps65917 and related nodes.
> The patch series is boot tested on DRA72-EVM.
>
> Thanks to Lokesh <lokeshvutla@ti.com> for testing the series.
For booting, this is dependent on recent hwmod fix patch series posted by me:
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg108001.html
Boot log for this series can be found here:
http://paste.ubuntu.com/7881545/
Thanks and regards,
Lokesh
>
> Keerthy J (2):
> ARM: dts: dra72-evm: Enable I2C1 node
> ARM: dts: dra72-evm: Add tps65917 PMIC node
>
> arch/arm/boot/dts/dra72-evm.dts | 120 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 120 insertions(+)
>
next prev parent reply other threads:[~2014-07-28 6:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 6:18 [PATCH 0/2] ARM: dts: dra72-evm: Add i2c1 and tps65917 nodes Keerthy
2014-07-28 6:18 ` [PATCH 1/2] ARM: dts: dra72-evm: Enable I2C1 node Keerthy
2014-07-28 9:24 ` Keerthy
2014-07-28 6:18 ` [PATCH 2/2] ARM: dts: dra72-evm: Add tps65917 PMIC node Keerthy
2014-07-28 9:23 ` Keerthy
2014-07-28 6:30 ` Lokesh Vutla [this message]
2014-07-28 9:22 ` [PATCH 0/2] ARM: dts: dra72-evm: Add i2c1 and tps65917 nodes Keerthy
2014-08-12 12:35 ` Keerthy
2014-09-08 20:04 ` Nishanth Menon
2014-09-08 23:12 ` Tony Lindgren
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=53D5EE21.1040000@ti.com \
--to=lokeshvutla@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=j-keerthy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-patch-review@list.ti.com \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=tony@atomide.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