From: "Paul E. McKenney" <paulmck@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
x86@kernel.org, feng.tang@intel.com, tglx@linutronix.de
Subject: [GIT PULL clocksource] Clocksource watchdog commits for v6.3 (to complete the set for v6.6)
Date: Sun, 27 Aug 2023 18:21:35 -0700 [thread overview]
Message-ID: <8016ce16-e049-4e27-9f98-29c52bb60145@paulmck-laptop> (raw)
Hello, Linus,
Once the v6.6 merge window opens, please pull these clocksource changes:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/clocksource.2023.08.15a
# HEAD: 233756a640be811efae33763db718fe29753b1e9: x86/tsc: Extend watchdog check exemption to 4-Sockets platform (2023-07-14 15:17:09 -0700)
Next merge window, I will take care to double-check beforehand to ensure
that the subject line does not assume that you have a time machine. In
the meantime, why not continue the trend? ;-)
----------------------------------------------------------------
Clocksource watchdog commits for v6.6
This pull reqeust contains the following:
o Handle negative skews in "skew is too large" messages.
o Extend watchdog check exemption to 4-Socket platforms
----------------------------------------------------------------
Feng Tang (1):
x86/tsc: Extend watchdog check exemption to 4-Sockets platform
Paul E. McKenney (1):
clocksource: Handle negative skews in "skew is too large" messages
arch/x86/kernel/tsc.c | 2 +-
kernel/time/clocksource.c | 8 ++++----
2 files changed, 5 insertions(+), 5 deletions(-)
next reply other threads:[~2023-08-28 1:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 1:21 Paul E. McKenney [this message]
2023-08-28 22:15 ` [GIT PULL clocksource] Clocksource watchdog commits for v6.3 (to complete the set for v6.6) pr-tracker-bot
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=8016ce16-e049-4e27-9f98-29c52bb60145@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=feng.tang@intel.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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).