From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: Keerthy <j-keerthy-l0cyMroinI0@public.gmane.org>
Cc: linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
t-kristo-l0cyMroinI0@public.gmane.org
Subject: Re: [PATCH 0/3] ARM: dts: am33xx: Add clock info to rtc nodes
Date: Wed, 9 Nov 2016 15:47:03 -0700 [thread overview]
Message-ID: <20161109224702.GN2428@atomide.com> (raw)
In-Reply-To: <b5aa9c3b-e922-404d-3e0a-8a84dd3bce2a-l0cyMroinI0@public.gmane.org>
* Keerthy <j-keerthy-l0cyMroinI0@public.gmane.org> [161106 21:25]:
>
>
> On Thursday 27 October 2016 11:18 AM, Keerthy wrote:
> > The series adds the clock info to rtc node.
> >
> > Boot tested and checked for rtc ticking on am335x-boneblack, am335x-bone
> > am437x-gp-evm.
>
> Tony,
>
> The relevant driver changes are already pulled by Alexandre Belloni.
> https://patchwork.kernel.org/patch/9398903/.
>
> Hope you call pull this set.
Applying into omap-for-v4.10/dt thanks.
Tony
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-11-09 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 5:48 [PATCH 0/3] ARM: dts: am33xx: Add clock info to rtc nodes Keerthy
[not found] ` <1477547288-5041-1-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-10-27 5:48 ` [PATCH 1/3] ARM: dts: AM335X-bone-common: Add the internal and external clock nodes for rtc Keerthy
2016-10-27 5:48 ` [PATCH 2/3] ARM: dts: AM335X-evm: " Keerthy
2016-10-27 5:48 ` [PATCH 3/3] ARM: dts: AM335X-evmsk: " Keerthy
2016-11-07 4:25 ` [PATCH 0/3] ARM: dts: am33xx: Add clock info to rtc nodes Keerthy
[not found] ` <b5aa9c3b-e922-404d-3e0a-8a84dd3bce2a-l0cyMroinI0@public.gmane.org>
2016-11-09 22:47 ` Tony Lindgren [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=20161109224702.GN2428@atomide.com \
--to=tony-4v6ys6ai5vpbdgjk7y7tuq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=j-keerthy-l0cyMroinI0@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=t-kristo-l0cyMroinI0@public.gmane.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).