linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org, john.stultz@linaro.org,
	kernel-team@fb.com, ak@linux.intel.com, rong.a.chen@intel.com,
	sboyd@kernel.org
Subject: [GIT PULL clocksource] Clocksource watchdog commits for v5.15
Date: Wed, 11 Aug 2021 17:01:33 -0700	[thread overview]
Message-ID: <20210812000133.GA402890@paulmck-ThinkPad-P17-Gen-1> (raw)

Hello, Thomas,

This pull request contains a single change that prevents clocksource
watchdog testing on systems with HZ < 100, thus preventing the integer
underflow that can occur on leisurely HZed systems.  This has been
posted to LKML:

https://lore.kernel.org/lkml/20210721212755.GA2066078@paulmck-ThinkPad-P17-Gen-1/

This has been tested by Rong Chen of Intel.  It has also been subjected
to subjected to the kbuild test robot and -next testing, and are available
in the git repository based on v5.14-rc2 at:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git clocksource

for you to fetch changes up to 9b073961afabcf70d0804e472ea02fc6c739dcce:

  clocksource: Prohibit clocksource watchdog test when HZ<100 (2021-07-20 13:54:34 -0700)

----------------------------------------------------------------
Paul E. McKenney (1):
      clocksource: Prohibit clocksource watchdog test when HZ<100

 lib/Kconfig.debug | 1 +
 1 file changed, 1 insertion(+)

             reply	other threads:[~2021-08-12  0:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12  0:01 Paul E. McKenney [this message]
2021-08-12 13:46 ` [GIT PULL clocksource] Clocksource watchdog commits for v5.15 Thomas Gleixner
2021-08-12 16:37   ` Paul E. McKenney
2021-08-12 17:11     ` Thomas Gleixner
2021-08-12 20:01       ` Paul E. McKenney

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=20210812000133.GA402890@paulmck-ThinkPad-P17-Gen-1 \
    --to=paulmck@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=john.stultz@linaro.org \
    --cc=kernel-team@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rong.a.chen@intel.com \
    --cc=sboyd@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).