From: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>
To: Suman Anna <s-anna@ti.com>, Santosh Shilimkar <ssantosh@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Franklin S Cooper Jr <fcooper@ti.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Nishanth Menon <nm@ti.com>,
Tero Kristo <t-kristo@ti.com>, Dave Gerlach <d-gerlach@ti.com>,
"Andrew F. Davis" <afd@ti.com>
Subject: Re: [PATCH 0/4] Add various TI-SCI DT nodes on 66AK2G SoCs
Date: Mon, 17 Jul 2017 21:47:33 -0700 [thread overview]
Message-ID: <33691a29-4a50-36e0-ad87-b5698d26bf77@oracle.com> (raw)
In-Reply-To: <20170718032844.29490-1-s-anna@ti.com>
On 7/17/17 8:28 PM, Suman Anna wrote:
> Hi Santosh,
>
> The following patch series adds various TI-SCI related DTS nodes that
> probe the corresponding TI-SCI genpd, clock and reset drivers for the
> 66AK2G platforms.
>
> This is the second of two series, and these nodes along with the defconfig
> patches finally allows adding other peripherals to the 66AK2G platforms.
> All the new peripherals should/will be added without using the device id
> macros [1]. Patches are baselined on 4.13-rc1 and are intended for the 4.14
> merge window.
>
And this one looks good as well. Please ping me if you don't see this
show up in next, by next week.
Regards,
Santosh
prev parent reply other threads:[~2017-07-18 4:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 3:28 Suman Anna
2017-07-18 3:28 ` [PATCH 1/4] ARM: dts: keystone-k2g: Add PMMC node to support TI-SCI protocol Suman Anna
2017-07-18 15:00 ` Andrew F. Davis
2017-07-18 23:50 ` Suman Anna
2017-07-19 15:25 ` Andrew F. Davis
2017-07-18 3:28 ` [PATCH 2/4] ARM: dts: keystone-k2g: Add ti-sci power domain node Suman Anna
2017-07-18 3:28 ` [PATCH 3/4] ARM: dts: keystone-k2g: Add ti-sci clock provider node Suman Anna
2017-07-18 3:28 ` [PATCH 4/4] ARM: dts: keystone-k2g: Add TI SCI reset-controller node Suman Anna
2017-07-18 4:47 ` santosh.shilimkar [this message]
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=33691a29-4a50-36e0-ad87-b5698d26bf77@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=afd@ti.com \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=fcooper@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.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
all inboxes | Powered by JetHome®