From: santosh.shilimkar@oracle.com
To: Grygorii Strashko <grygorii.strashko@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>
Cc: Sekhar Nori <nsekhar@ti.com>,
Murali Karicheri <m-karicheri2@ti.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND PATCH next v2 0/6] ARM: keystone: update dt and enable cpts support
Date: Thu, 5 Sep 2019 21:52:03 -0700 [thread overview]
Message-ID: <56a97316-73aa-b8ba-41f3-a374a14edc92@oracle.com> (raw)
In-Reply-To: <323c1835-e6b0-9153-8d1e-06200d5e2201@ti.com>
On 9/5/19 12:33 PM, Grygorii Strashko wrote:
> Hi Santosh,
>
> On 06/07/2019 02:48, santosh.shilimkar@oracle.com wrote:
>> On 7/5/19 8:12 AM, Grygorii Strashko wrote:
>>> Hi Santosh,
>>>
>>> This series is set of platform changes required to enable NETCP CPTS
>>> reference
>>> clock selection and final patch to enable CPTS for Keystone
>>> 66AK2E/L/HK SoCs.
>>>
>>> Those patches were posted already [1] together with driver's changes,
>>> so this
>>> is re-send of DT/platform specific changes only, as driver's changes
>>> have
>>> been merged already.
>>>
>>> Patches 1-5: CPTS DT nodes update for TI Keystone 2 66AK2HK/E/L SoCs.
>>> Patch 6: enables CPTS for TI Keystone 2 66AK2HK/E/L SoCs.
>>>
>>> [1] https://patchwork.kernel.org/cover/10980037/
>>>
>>> Grygorii Strashko (6):
>>> ARM: dts: keystone-clocks: add input fixed clocks
>>> ARM: dts: k2e-clocks: add input ext. fixed clocks tsipclka/b
>>> ARM: dts: k2e-netcp: add cpts refclk_mux node
>>> ARM: dts: k2hk-netcp: add cpts refclk_mux node
>>> ARM: dts: k2l-netcp: add cpts refclk_mux node
>>> ARM: configs: keystone: enable cpts
>>>
>> Will add these for 5.4 queue. Thanks !!
>
> Sry, that I'm disturbing you, but I do not see those patches applied?
>
Sorry I missed this one. Will queue this up for next merge window.
Will push this out to next early once rc1 is out. If you don't
see it, please ping me.
Regards,
Santosh
prev parent reply other threads:[~2019-09-06 4:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 15:12 [RESEND PATCH next v2 0/6] ARM: keystone: update dt and enable cpts support Grygorii Strashko
2019-07-05 15:12 ` [RESEND PATCH next v2 1/6] ARM: dts: keystone-clocks: add input fixed clocks Grygorii Strashko
2019-07-05 15:12 ` [RESEND PATCH next v2 2/6] ARM: dts: k2e-clocks: add input ext. fixed clocks tsipclka/b Grygorii Strashko
2019-07-05 15:12 ` [RESEND PATCH next v2 3/6] ARM: dts: k2e-netcp: add cpts refclk_mux node Grygorii Strashko
2019-07-05 15:12 ` [RESEND PATCH next v2 4/6] ARM: dts: k2hk-netcp: " Grygorii Strashko
2019-07-05 15:12 ` [RESEND PATCH next v2 5/6] ARM: dts: k2l-netcp: " Grygorii Strashko
2019-07-05 15:12 ` [RESEND PATCH next v2 6/6] ARM: configs: keystone: enable cpts Grygorii Strashko
2019-07-05 23:48 ` [RESEND PATCH next v2 0/6] ARM: keystone: update dt and enable cpts support santosh.shilimkar
2019-07-16 10:44 ` grygorii
2019-09-05 19:33 ` Grygorii Strashko
2019-09-06 4:52 ` 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=56a97316-73aa-b8ba-41f3-a374a14edc92@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=nsekhar@ti.com \
--cc=ssantosh@kernel.org \
/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).