From: Nishanth Menon <nm@ti.com>
To: Keerthy <a0393675@ti.com>
Cc: <tony@atomide.com>, Keerthy <j-keerthy@ti.com>,
<mark.rutland@arm.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<galak@codeaurora.org>, Lokesh Vutla <lokeshvutla@ti.com>
Subject: Re: [PATCH 0/2] ARM: dts: dra72-evm: Add i2c1 and tps65917 nodes
Date: Mon, 8 Sep 2014 15:04:43 -0500 [thread overview]
Message-ID: <20140908200443.GA24258@kahuna> (raw)
In-Reply-To: <53EA0A26.1050301@ti.com>
On 18:05-20140812, Keerthy wrote:
> On Monday 28 July 2014 02:52 PM, Keerthy wrote:
> >On Monday 28 July 2014 12:00 PM, Lokesh Vutla wrote:
> >>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.
> >
> >Correcting the 'to' list.
>
> Hi Tony,
>
> If there are no comments could you please pull these two patches?
With 3.17-rc4, I tested this series:
dra72-evm-before: http://paste.ubuntu.org.cn/1496342
dra72-evm-after: http://paste.ubuntu.org.cn/1496341
Patches:
https://patchwork.kernel.org/patch/4632391/
https://patchwork.kernel.org/patch/4632421/
Could we pick these with 3.18?
Please free to add:
Tested-by: Nishanth Menon <nm@ti.com>
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2014-09-08 20:04 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 ` [PATCH 0/2] ARM: dts: dra72-evm: Add i2c1 and tps65917 nodes Lokesh Vutla
2014-07-28 9:22 ` Keerthy
2014-08-12 12:35 ` Keerthy
2014-09-08 20:04 ` Nishanth Menon [this message]
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=20140908200443.GA24258@kahuna \
--to=nm@ti.com \
--cc=a0393675@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=lokeshvutla@ti.com \
--cc=mark.rutland@arm.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