From: Thomas Gleixner <tglx@kernel.org>
To: Waiman Long <llong@redhat.com>, Jiri Wiesner <jwiesner@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Feng Tang <feng.tang@intel.com>, John Stultz <jstultz@google.com>,
Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH] clocksource: Use same threshold for read-back delay and time skew
Date: Sun, 18 Jan 2026 10:34:35 +0100 [thread overview]
Message-ID: <875x8z2ris.ffs@tglx> (raw)
In-Reply-To: <cccef2a0-9267-47c1-871a-f3a1a9d9678d@redhat.com>
On Fri, Jan 16 2026 at 15:05, Waiman Long wrote:
> On 1/16/26 1:08 PM, Jiri Wiesner wrote:
> I think wd_seq_delay should compare to just one
> watchdog->uncertainty_margin. See my comment on a related patch sent out
> by Thomas.
>
> https://lore.kernel.org/lkml/8178bbf3-4a9d-4add-93bb-2ebd4dc03e9f@redhat.com/
Duh. I completely forgot about that one....
next prev parent reply other threads:[~2026-01-18 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 18:08 [PATCH] clocksource: Use same threshold for read-back delay and time skew Jiri Wiesner
2026-01-16 20:05 ` Waiman Long
2026-01-18 9:34 ` Thomas Gleixner [this message]
2026-01-22 9:43 ` Jiri Wiesner
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=875x8z2ris.ffs@tglx \
--to=tglx@kernel.org \
--cc=feng.tang@intel.com \
--cc=jstultz@google.com \
--cc=jwiesner@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=llong@redhat.com \
--cc=paulmck@kernel.org \
--cc=sboyd@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