public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: David Woodhouse <dwmw2@infradead.org>,
	Alexander Graf <graf@amazon.com>, Sasha Levin <sashal@kernel.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, "Clemens Ladisch" <clemens@ladisch.de>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	"Borislav Petkov" <bp@alien8.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Pasha Tatashin" <pasha.tatashin@soleen.com>,
	nh-open-source@amazon.com,
	"Nicolas Saenz Julienne" <nsaenz@amazon.es>,
	"Hendrik Borghorst" <hborghor@amazon.de>,
	"Filippo Sironi" <sironi@amazon.de>,
	"Jan Schönherr" <jschoenh@amazon.de>,
	ricardo.neri-calderon@linux.intel.com
Subject: Re: [PATCH 2/2] hpet: Add HPET-based NMI watchdog support
Date: Wed, 04 Feb 2026 11:34:18 +0100	[thread overview]
Message-ID: <87zf5o23x1.ffs@tglx> (raw)
In-Reply-To: <4539d23f9f857da28d3414f512afe3c8bfe6c426.camel@infradead.org>

On Tue, Feb 03 2026 at 23:13, David Woodhouse wrote:
> On Tue, 2026-02-03 at 21:46 +0100, Thomas Gleixner wrote:
>> On Tue, Feb 03 2026 at 17:43, David Woodhouse wrote:
>> > Honestly, even when I've explicitly told Kiro three times *not* to do
>> > something, *and* implemented a git commit hook to catch it out, it has
>> > a tendency just to automatically override the commit hook!
>> 
>> Anarchic Intelligence :)
>> 
>> > If it was made of meat, I'd have stabbed it by now.
>> 
>> rm -rf solves that problem too once and forever.
>
> There *are* cases where it's actually an accelerating function,
> especially where there's a bunch of boilerplate/infrastructure code to
> be generated. But by $DEITY you have to keep a close eye on it. It has
> absolutely no taste whatsoever.
>
> And I've watched it spend quarter of an hour failing to use its own
> file read/write tools to edit C files, falling back to sed and then
> python scripts to make the simple changes it wanted to make. Sometimes
> needing to be prompted because it thought its sed script had worked
> when in fact it hadn't. It's... impressive :)

You clearly proved the point that this is accelerating the time and
energy waste.

      reply	other threads:[~2026-02-04 10:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02 17:48 [PATCH 0/2] Add HPET NMI Watchdog support Alexander Graf
2026-02-02 17:48 ` [PATCH 1/2] x86/ioapic: Add NMI delivery configuration helper Alexander Graf
2026-02-03 10:08   ` Thomas Gleixner
2026-02-03 10:44     ` Alexander Graf
2026-02-03 10:45     ` David Woodhouse
2026-02-02 17:48 ` [PATCH 2/2] hpet: Add HPET-based NMI watchdog support Alexander Graf
2026-02-03 10:32   ` Thomas Gleixner
2026-02-03 12:36     ` Alexander Graf
2026-02-03 15:28       ` Thomas Gleixner
2026-02-03 19:44         ` Ricardo Neri
2026-02-03 20:49           ` Thomas Gleixner
2026-02-04  5:05             ` Ricardo Neri
2026-02-03 16:24       ` Sasha Levin
2026-02-03 17:19         ` Alexander Graf
2026-02-03 17:43           ` David Woodhouse
2026-02-03 20:46             ` Thomas Gleixner
2026-02-03 23:13               ` David Woodhouse
2026-02-04 10:34                 ` 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=87zf5o23x1.ffs@tglx \
    --to=tglx@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=clemens@ladisch.de \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=graf@amazon.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hborghor@amazon.de \
    --cc=jschoenh@amazon.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nh-open-source@amazon.com \
    --cc=nsaenz@amazon.es \
    --cc=pasha.tatashin@soleen.com \
    --cc=pbonzini@redhat.com \
    --cc=ricardo.neri-calderon@linux.intel.com \
    --cc=sashal@kernel.org \
    --cc=sironi@amazon.de \
    --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