From: Jihong Min <hurryman2212@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-api@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] docs: hwmon: Document the uhwmon userspace interface
Date: Mon, 19 Oct 2026 02:30:39 +0900 [thread overview]
Message-ID: <fe746c04-391e-4b7e-a5c9-7dfd3cd07913@gmail.com> (raw)
In-Reply-To: <e77719ee-c813-400e-b49a-9f8a3b0e2e91@roeck-us.net>
Ok. Then I will withdraw these patch series.
But then let me ask you the initial question that brought this patch
series: Do you think it is at least OK to add kernel drivers for
network-based sensors? Or do you think those are also to be subjected to
be rejected (or remained in DKMS projects)?
Sincerely,
Jihong Min
On 10/19/26 01:06, Guenter Roeck wrote:
> On Sat, Oct 10, 2026 at 12:38:44AM +0900, Jihong Min wrote:
>> Document the uhwmon UAPI for developers implementing userspace hwmon
>> drivers. Cover device registration, request handling, notifications
>> and device lifetime.
>>
>> Assisted-by: Codex:gpt-6-astra
>> Signed-off-by: Jihong Min <hurryman2212@gmail.com>
>
> I am not going to review, much less apply, this series.
> Exposing subsystem internals to userspace is a bad idea and would limit
> future improvements of the hardware monitoring subsystem. User space file
> systems are bad enough and cause all kinds of trouble. I don't want to have
> to deal with the same kind of issues in the hardware monitoring subsystem.
>
> Interested parties should implement kernel hardware monitoring
> drivers instead.
>
> Guenter
next prev parent reply other threads:[~2026-10-18 17:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 15:38 [PATCH 0/5] hwmon: Introduce uhwmon for userspace implementations Jihong Min
2026-10-09 15:38 ` [PATCH 1/5] hwmon: Export sensor and attribute definitions to userspace Jihong Min
2026-10-09 15:49 ` sashiko-bot
2026-10-18 15:52 ` Guenter Roeck
2026-10-09 15:38 ` [PATCH 2/5] hwmon: Expose attribute validation and string helpers Jihong Min
2026-10-09 15:47 ` sashiko-bot
2026-10-09 15:38 ` [PATCH 3/5] hwmon: Add a generic interface for userspace implementations Jihong Min
2026-10-09 15:56 ` sashiko-bot
2026-10-10 14:50 ` Markus Elfring
2026-10-09 15:38 ` [PATCH 4/5] hwmon: Reject truncated attribute names Jihong Min
2026-10-09 15:44 ` sashiko-bot
2026-10-09 15:38 ` [PATCH 5/5] docs: hwmon: Document the uhwmon userspace interface Jihong Min
2026-10-09 15:55 ` sashiko-bot
2026-10-18 16:06 ` Guenter Roeck
2026-10-18 17:30 ` Jihong Min [this message]
[not found] ` <CAAwencqEVCjtnJfmnut2zXXPvuwju5T89FDSpHN3wPfrrJnRdQ@mail.gmail.com>
2026-10-19 22:38 ` Guenter Roeck
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=fe746c04-391e-4b7e-a5c9-7dfd3cd07913@gmail.com \
--to=hurryman2212@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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