From: Keerthy <a0393675@ti.com>
To: Tony Lindgren <tony@atomide.com>, broonie@kernel.org
Cc: Keerthy <j-keerthy@ti.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, mark.rutland@arm.com,
galak@codeaurora.org, robh+dt@kernel.org, linux@arm.linux.org.uk,
balbi@ti.com, kishon@ti.com
Subject: Re: [PATCH v3 0/7] ARM: dts: AM43x: Add devcice tree nodes
Date: Thu, 10 Jul 2014 18:55:22 +0530 [thread overview]
Message-ID: <53BE9442.4070101@ti.com> (raw)
In-Reply-To: <20140709115106.GV28884@atomide.com>
On Wednesday 09 July 2014 05:21 PM, Tony Lindgren wrote:
> * Keerthy <a0393675@ti.com> [140709 04:03]:
>> On Wednesday 09 July 2014 02:01 PM, Tony Lindgren wrote:
>>> * Keerthy <j-keerthy@ti.com> [140708 22:40]:
>>>> The patch series adds the device tree nodes and the corresponding
>>>> documentation. The series also enabled tps65218 config options
>>>> in the omap2plus_defconfig.
>>>>
>>>> The series is boot tested on both AM43x-epos-evm and AM437x-gp-evm.
>>> Are the .dts changes safe to apply separately without breaking
>>> anything?
>> Tony,
>>
>> Patch 1/7 had to be re-based on Mark's latest branch for tps65218.
>> Other patches can be taken as is. These patches are boot tested on
>> both am437x-gp-evm and am43x-epos-evm.
> OK thanks applying patches 4 - 7 into omap-for-v3.17/dt.
>
> Tony
Thanks Tony.
Mark,
Could you please pull patch 2 and patch 3? The documentation is missing.
Kind Regards,
Keerthy
next prev parent reply other threads:[~2014-07-10 13:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 5:36 [PATCH v3 0/7] ARM: dts: AM43x: Add devcice tree nodes Keerthy
2014-07-09 5:36 ` [PATCH v3 1/7] regulator: tps65218: Add fixed_uV fields for dcdc5 and dcdc6 Keerthy
2014-07-09 9:14 ` Mark Brown
2014-07-09 9:36 ` Keerthy
[not found] ` <1404884193-20580-2-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2014-07-09 10:22 ` [PATCH v4] " Keerthy
2014-07-10 12:12 ` Mark Brown
2014-07-10 13:10 ` Keerthy
2014-07-10 14:50 ` Mark Brown
2014-07-09 5:36 ` [PATCH v3 2/7] mfd: Add DT bindings for tps65218 PMIC Keerthy
2014-07-09 5:36 ` [PATCH v3 3/7] regulator: Add DT bindings for tps65218 PMIC regulators Keerthy
2014-07-09 5:36 ` [PATCH v3 4/7] ARM: dts: AM43x: Add TPS65218 device tree nodes Keerthy
2014-07-09 5:36 ` [PATCH v3 5/7] ARM: dts: AM437x: Fix i2c nodes indentation Keerthy
2014-07-09 5:36 ` [PATCH v3 6/7] ARM: dts: AM437x: Add TPS65218 device tree nodes Keerthy
2014-07-09 5:36 ` [PATCH v3 7/7] ARM: configs: omap2plus_defconfig: enable TPS65218 configs Keerthy
2014-07-09 8:31 ` [PATCH v3 0/7] ARM: dts: AM43x: Add devcice tree nodes Tony Lindgren
[not found] ` <20140709083114.GH28884-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2014-07-09 10:59 ` Keerthy
[not found] ` <53BD208E.6000507-l0cyMroinI0@public.gmane.org>
2014-07-09 11:51 ` Tony Lindgren
2014-07-10 13:25 ` Keerthy [this message]
[not found] ` <53BE9442.4070101-l0cyMroinI0@public.gmane.org>
2014-07-10 13:50 ` Keerthy
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=53BE9442.4070101@ti.com \
--to=a0393675@ti.com \
--cc=balbi@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=j-keerthy@ti.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).