From: Baolin Wang <baolin.wang@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Xunlei Pang" <pang.xunlei@linaro.org>,
peterz@infradead.org, benh@kernel.crashing.org,
heiko.carstens@de.ibm.com, paulus@samba.org,
"Jeffrey Vander Stoep" <jeffv@google.com>,
cl@linux.com, mark.d.rustad@intel.com,
"Heena Sirwani" <heenasirwani@gmail.com>,
linux-arch@vger.kernel.org, linux-s390@vger.kernel.org,
"y2038 Mailman List" <y2038@lists.linaro.org>,
mpe@ellerman.id.au, rafael.j.wysocki@intel.com,
"Andrew Hunter" <ahh@google.com>,
tiwai@suse.de, "Jeffrey Layton" <jlayton@primarydata.com>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Paul Turner" <pjt@google.com>,
serge@hallyn.com, "Serge Hallyn" <serge.hallyn@canonical.com>,
riel@redhat.com, "Kees Cook" <keescook@chromium.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Richard Cochran" <richardcochran@gmail.com>,
schwidefsky@de.ibm.com, "John Stultz" <john.stultz@linaro.org>,
james.l.morris@oracle.com, rth@twiddle.net, sds@tyc
Subject: Re: [PATCH v4 00/25] Convert the posix_clock_operations and k_clock structure to ready for 2038
Date: Wed, 3 Jun 2015 10:13:24 +0800 [thread overview]
Message-ID: <CAMz4ku+8unOm7EpZyurO+mzUywTJWJng_NFMAfcD8jPMHQAneg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1506022115240.20347@nanos>
On 3 June 2015 at 03:20, Thomas Gleixner <tglx@linutronix.de> wrote:
> On Mon, 1 Jun 2015, Baolin Wang wrote:
>
> > This patch series changes the 32-bit time types (timespec/itimerspec) to
> > the 64-bit types (timespec64/itimerspec64), since 32-bit time types will
> > break in the year 2038.
>
> That's only true for 32bit systems.
>
> All in all the patch series looks rather reasonable now, except for
> the subject lines and the changelogs.
>
> The only technical objection I have is the macro conversion magic in
> patch #6. This can be done in a less cryptic and more efficient way.
>
> See the comments to the various patches and please apply them to all
> of the series.
>
> Thanks,
>
> tglx
>
>
>
Hi Thomas,
Thanks for your comments, and i'll check and fix these problems.
--
Baolin.wang
Best Regards
_______________________________________________
Y2038 mailing list
Y2038@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/y2038
prev parent reply other threads:[~2015-06-03 2:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 11:44 [PATCH v4 00/25] Convert the posix_clock_operations and k_clock structure to ready for 2038 Baolin Wang
2015-06-01 11:44 ` Baolin Wang
2015-06-02 19:19 ` Thomas Gleixner
2015-06-02 19:19 ` Thomas Gleixner
2015-06-02 19:20 ` Thomas Gleixner
2015-06-02 19:20 ` Thomas Gleixner
2015-06-03 2:13 ` Baolin Wang [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=CAMz4ku+8unOm7EpZyurO+mzUywTJWJng_NFMAfcD8jPMHQAneg@mail.gmail.com \
--to=baolin.wang@linaro.org \
--cc=ahh@google.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=cl@linux.com \
--cc=fweisbec@gmail.com \
--cc=heenasirwani@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=james.l.morris@oracle.com \
--cc=jeffv@google.com \
--cc=jlayton@primarydata.com \
--cc=john.stultz@linaro.org \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mark.d.rustad@intel.com \
--cc=mpe@ellerman.id.au \
--cc=pang.xunlei@linaro.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rafael.j.wysocki@intel.com \
--cc=richardcochran@gmail.com \
--cc=riel@redhat.com \
--cc=rth@twiddle.net \
--cc=schwidefsky@de.ibm.com \
--cc=sds@tyc \
--cc=serge.hallyn@canonical.com \
--cc=serge@hallyn.com \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.de \
--cc=y2038@lists.linaro.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).