From: John Stultz <john.stultz@linaro.org>
To: "pang.xunlei" <pang.xunlei@zte.com.cn>
Cc: lkml <linux-kernel@vger.kernel.org>,
Alessandro Zummo <a.zummo@towertech.it>,
Arnd Bergmann <arnd@arndb.de>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
linux390@de.ibm.com, Xunlei Pang <pang.xunlei@linaro.org>,
Ralf Baechle <ralf@linux-mips.org>,
"rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Thomas Gleixner <tglx@linutronix.de>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH 1/8] time: Add y2038 safe read_boot_clock64()
Date: Wed, 18 Mar 2015 09:30:40 -0700 [thread overview]
Message-ID: <CALAqxLXB+TKTkrAhtW=Pn2h0KZR2Yazd8ojTNj0D7V9OxL96Lg@mail.gmail.com> (raw)
In-Reply-To: <OF2C7428FA.095162DD-ON48257E0C.004641E0-48257E0C.004652BC@zte.com.cn>
On Wed, Mar 18, 2015 at 5:48 AM, <pang.xunlei@zte.com.cn> wrote:
> Ping ...
Thanks for the reminder. Since there's not been any objections, I'm
queuing this up.
thanks
-john
next prev parent reply other threads:[~2015-03-18 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 3:15 [PATCH 0/8] Add y2038 safe replacements for read_boot_clock(), read_persistent_clock() and update_persistent_clock() Xunlei Pang
[not found] ` <1426043715-22043-1-git-send-email-xlpang-KN7UnAbNpbg@public.gmane.org>
2015-03-11 3:15 ` [PATCH 1/8] time: Add y2038 safe read_boot_clock64() Xunlei Pang
[not found] ` <OF2C7428FA.095162DD-ON48257E0C.004641E0-48257E0C.004652BC@zte.com.cn>
2015-03-18 16:30 ` John Stultz [this message]
2015-03-11 3:15 ` [PATCH 2/8] time: Add y2038 safe read_persistent_clock64() Xunlei Pang
2015-03-11 3:15 ` [PATCH 3/8] time: Add y2038 safe update_persistent_clock64() Xunlei Pang
2015-03-11 3:15 ` [PATCH 4/8] ARM: OMAP: 32k counter: Provide y2038-safe omap_read_persistent_clock() replacement Xunlei Pang
2015-03-11 15:28 ` 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='CALAqxLXB+TKTkrAhtW=Pn2h0KZR2Yazd8ojTNj0D7V9OxL96Lg@mail.gmail.com' \
--to=john.stultz@linaro.org \
--cc=a.zummo@towertech.it \
--cc=arnd.bergmann@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=pang.xunlei@linaro.org \
--cc=pang.xunlei@zte.com.cn \
--cc=ralf@linux-mips.org \
--cc=rtc-linux@googlegroups.com \
--cc=schwidefsky@de.ibm.com \
--cc=swarren@wwwdotorg.org \
--cc=tglx@linutronix.de \
--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).