public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: connordw@amazon.com
Cc: connordw@amazon.com, jstultz@google.com,
	linux-kernel@vger.kernel.org, nh-open-source@amazon.com,
	paulmck@kernel.org, sboyd@kernel.org
Subject: Re: [PATCH timers/core v1] clocksource: Align clocksource watchdog constraints with Kconfig value
Date: Mon, 23 Mar 2026 20:59:06 +0100	[thread overview]
Message-ID: <877br2iagl.ffs@tglx> (raw)
In-Reply-To: <20260323132808.78343-1-connordw@amazon.com>

On Mon, Mar 23 2026 at 13:28, connordw@amazon.com wrote:
> On Fri, Mar 20 2026 at 17:58 (+0100), Thomas Gleixner wrote:
>> The only valid "fix" is to delete the dead code and not to polish it,
>> but that's pretty moot as it is harmless and already scheduled for
>> removal in 7.1 due to:
>> 
>>   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=timers/core
>
> Please withdraw my patch. Thanks for your response, I wasn't aware that
> despite cs->uncertainty_margin being set when CLOCKSOURCE_WATCHDOG=n it
> wasn't subsequently being read anywhere upstream. Since this logic will be
> removed in v7.1 anyway this patch is indeed pointless.
>
> Apologies for the noise,

Nothing to apologize for.

      reply	other threads:[~2026-03-23 19:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 14:29 [PATCH timers/core v1] clocksource: Align clocksource watchdog constraints with Kconfig value Connor Williamson
2026-03-20 16:58 ` Thomas Gleixner
2026-03-23 13:28   ` connordw
2026-03-23 19:59     ` Thomas Gleixner [this message]

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=877br2iagl.ffs@tglx \
    --to=tglx@kernel.org \
    --cc=connordw@amazon.com \
    --cc=jstultz@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nh-open-source@amazon.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