mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: skxby <2374604267@qq.com>
To: Donjuanplatinum <donplat@barrensea.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
	rust-for-linux@vger.kernel.org
Subject: Re: [PATCH 0/2] rust: hwmon: rework hwmon abstractions, add TMP108 driver
Date: Sat, 17 Oct 2026 09:38:20 +0800	[thread overview]
Message-ID: <tencent_3A4DA800AA0FC8C76CB748048FFA0DCC210A@qq.com> (raw)
In-Reply-To: <818d5dd7-4b8f-488d-ad99-3ce114027262@roeck-us.net>

Hi Donjuanplatinum, hi Guenter,

An apology first: the AI-written reply in this thread was sent without my
review. That was a mistake, and I am sorry. Nothing further goes out from
here without going through me first.

Your "?" was about the "<SENDER NAME>" line at the end of our cover letter.
That was a placeholder in our sending template that should have been
replaced before posting -- there is nothing hidden behind it.

Guenter, on runtime testing: every patch in this series was built and run.
The lifecycle stress tests (100x load/unload cycles), a 22-case sysfs
regression, and extreme-value writes were part of the work from the start;
they are how the chip_config terminator and the i2c client leak on the
registration error path were pinned down, and they were used to reproduce
and verify every fix. The defects the review raised that the tests had not
caught were handled the same way: reproduce first, then fix, then re-run.

v2 is being finalized: it addresses all review findings, will Cc
rust-for-linux, and carries an "Assisted-by: LLM" tag per
Documentation/process/coding-assistants.html.

Before posting it: are the two of you still willing to take a look? If the
answer is no, I would rather hear that now.

skxby


      reply	other threads:[~2026-10-17  1:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12 15:57 [RFC PATCH] rust: hwmon: add basic hwmon abstractions Donjuanplatinum
2026-05-12 16:30 ` Guenter Roeck
2026-10-16  7:24   ` [PATCH 0/2] rust: hwmon: rework hwmon abstractions, add TMP108 driver skxby
2026-10-16  8:11     ` Donjuanplatinum
     [not found]       ` <179214016501.15268.642738678844764524@qq.com>
2026-10-16  8:42       ` skxby
2026-10-16 16:16     ` Guenter Roeck
2026-10-17  1:38       ` skxby [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=tencent_3A4DA800AA0FC8C76CB748048FFA0DCC210A@qq.com \
    --to=2374604267@qq.com \
    --cc=donplat@barrensea.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=rust-for-linux@vger.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

all inboxes | Powered by JetHome®