From: Arnd Bergmann <arnd@arndb.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Heena Sirwani <heenasirwani@gmail.com>,
linux-kernel@vger.kernel.org, john.stultz@linaro.org
Subject: Re: [PATCH v2] timekeeping: Added a function to return tv_sec portion of ktime_get_real_ts64()
Date: Tue, 28 Oct 2014 21:35:08 +0100 [thread overview]
Message-ID: <1825407.TtFpTslzjC@wuerfel> (raw)
In-Reply-To: <alpine.DEB.2.11.1410282123450.5308@nanos>
On Tuesday 28 October 2014 21:31:32 Thomas Gleixner wrote:
> On Tue, 28 Oct 2014, Arnd Bergmann wrote:
> > On Tuesday 28 October 2014 18:13:09 Thomas Gleixner wrote:
> > I'd like to apply this patch to my y2038 branch and apply the
> > other patches that need it on top, unless you want to still submit
> > it for 3.18.
>
> I think I should take these patches for 3.18. We do not create users
> yet, but it makes it easier for submaintaners to apply stuff which you
> convert. And it lets me have the whole core lot together with other
> changes in that area. I create a seperate branch which you can pull
> from.
Ok, sounds good.
> > Regarding the names, should we then have
> >
> > time64_t ktime_get_real_seconds(void);
> > time64_t ktime_get_seconds(void);
>
> I like that one. Moving all the time interfaces to a ktime_ prefix and
> let the default implementation as CLOCK_MONOTONIC and the others with
> the added '_real', '_boot' ... describe their CLOCK_WHATEVER property
> makes it pretty clear.
Good. So you can apply this patch as-is and Heena will get you the
other one.
Thanks!
Arnd
next prev parent reply other threads:[~2014-10-28 20:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 5:08 [PATCH v2] timekeeping: Added a function to return tv_sec portion of ktime_get_real_ts64() Heena Sirwani
2014-10-28 15:43 ` Thomas Gleixner
2014-10-28 15:50 ` Arnd Bergmann
2014-10-28 17:13 ` Thomas Gleixner
2014-10-28 19:54 ` Arnd Bergmann
2014-10-28 20:31 ` Thomas Gleixner
2014-10-28 20:35 ` Arnd Bergmann [this message]
2014-10-28 20:52 ` Thomas Gleixner
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=1825407.TtFpTslzjC@wuerfel \
--to=arnd@arndb.de \
--cc=heenasirwani@gmail.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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