From: Guenter Roeck <linux@roeck-us.net>
To: skxby <2374604267@qq.com>
Cc: Donjuanplatinum <donplat@barrensea.org>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] rust: hwmon: rework hwmon abstractions, add TMP108 driver
Date: Fri, 16 Oct 2026 09:16:29 -0700 [thread overview]
Message-ID: <818d5dd7-4b8f-488d-ad99-3ce114027262@roeck-us.net> (raw)
In-Reply-To: <tencent_576573331343805F032731492D63C12D7E08@qq.com>
On 10/16/26 00:24, skxby wrote:
> Hi Guenter,
>
> [1] Positioning
>
> This series follows up on Donjuanplatinum's RFC [1], which proposed basic
> Rust abstractions for the hwmon subsystem. Your reply [2] noted that Rust
> support in hwmon would have to wait for someone else to pick up
> maintainership, and the thread has been quiet since. I am not re-litigating
> that decision here. I have taken the proposed abstractions, reworked them
> against the current rust tree, and written a real driver on top of them
> (TMP108, mirroring drivers/hwmon/tmp108.c). I am posting the result so the
> work itself - the shape of the abstraction and the driver built on it - can
> be looked at on its own merits, whenever and by whoever takes the
> maintainership question up.
>
By now I add a new concern: Much of the Rust code I have seen as been written
by or heavily guided by AI. I even heard the argument that Rust code written
that way would not have tho be runtime tested since its inherent support
for self-tests and the ability of AI code review would already ensure its
quality. I do not believe that hype. Others will have to accept it.
Guenter
next prev parent reply other threads:[~2026-10-16 16:16 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 [this message]
2026-10-17 1:38 ` skxby
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=818d5dd7-4b8f-488d-ad99-3ce114027262@roeck-us.net \
--to=linux@roeck-us.net \
--cc=2374604267@qq.com \
--cc=donplat@barrensea.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@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®