From: Christian Borntraeger <borntraeger@de.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Pavel Tatashin <pasha.tatashin@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH] timekeeping: Fix declaration of read_persistent_wall_and_boot_offset
Date: Mon, 3 Sep 2018 10:15:33 +0200 [thread overview]
Message-ID: <20180903081533.34366-1-borntraeger@de.ibm.com> (raw)
it is
read_persistent_wall_and_boot_offset and not
read_persistent_clock_and_boot_offset
Fixes: 3eca993740b8eb40f51 ("timekeeping: Replace read_boot_clock64() with read_persistent_wall_and_boot_offset()")
CC: Pavel Tatashin <pasha.tatashin@oracle.com>
CC: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
---
include/linux/timekeeping.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/timekeeping.h b/include/linux/timekeeping.h
index 5d738804e3d6..a5a3cfc3c2fa 100644
--- a/include/linux/timekeeping.h
+++ b/include/linux/timekeeping.h
@@ -258,8 +258,8 @@ extern void ktime_get_snapshot(struct system_time_snapshot *systime_snapshot);
extern int persistent_clock_is_local;
extern void read_persistent_clock64(struct timespec64 *ts);
-void read_persistent_clock_and_boot_offset(struct timespec64 *wall_clock,
- struct timespec64 *boot_offset);
+void read_persistent_wall_and_boot_offset(struct timespec64 *wall_clock,
+ struct timespec64 *boot_offset);
extern int update_persistent_clock64(struct timespec64 now);
/*
--
2.17.0
next reply other threads:[~2018-09-03 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 8:15 Christian Borntraeger [this message]
2018-09-03 11:30 ` [tip:timers/urgent] timekeeping: Fix declaration of read_persistent_wall_and_boot_offset() tip-bot for Christian Borntraeger
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=20180903081533.34366-1-borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pasha.tatashin@oracle.com \
--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
all inboxes | Powered by JetHome®