From: Arnd Bergmann <arnd@arndb.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v5 3/3] timekeeping: add missing _ns functions for coarse accessors
Date: Fri, 21 Jun 2019 22:45:48 +0200 [thread overview]
Message-ID: <CAK8P3a2mQpC-+iON976gYgyX_tVJMiaVO3rbCx+y_543QhjC7w@mail.gmail.com> (raw)
In-Reply-To: <20190621203249.3909-3-Jason@zx2c4.com>
On Fri, Jun 21, 2019 at 10:33 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> This further unifies the accessors for the fast and coarse functions, so
> that the same types of functions are available for each. There was also
> a bit of confusion with the documentation, which prior advertised a
> function that has never existed. Finally, the vanilla ktime_get_coarse()
> was omitted from the API originally, so this fills this oversight.
>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> Cc: Arnd Bergmann <arnd@arndb.de>
All three patches
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Thanks for the cleanup and your patience.
Arnd
next prev parent reply other threads:[~2019-06-21 20:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 20:32 [PATCH v5 1/3] timekeeping: use proper ktime_add when adding nsecs in coarse offset Jason A. Donenfeld
2019-06-21 20:32 ` [PATCH v5 2/3] timekeeping: use proper clock specifier names in functions Jason A. Donenfeld
2019-06-22 19:29 ` [tip:timers/core] timekeeping: Use " tip-bot for Jason A. Donenfeld
2019-06-21 20:32 ` [PATCH v5 3/3] timekeeping: add missing _ns functions for coarse accessors Jason A. Donenfeld
2019-06-21 20:45 ` Arnd Bergmann [this message]
2019-06-22 19:29 ` [tip:timers/core] timekeeping: Add " tip-bot for Jason A. Donenfeld
2019-06-22 19:28 ` [tip:timers/core] timekeeping: Use proper ktime_add when adding nsecs in coarse offset tip-bot for Jason A. Donenfeld
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=CAK8P3a2mQpC-+iON976gYgyX_tVJMiaVO3rbCx+y_543QhjC7w@mail.gmail.com \
--to=arnd@arndb.de \
--cc=Jason@zx2c4.com \
--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;
as well as URLs for NNTP newsgroup(s).