linux-kernel - Re: [PATCH] hwmon: it87: describe per-chip temperature resources

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAGHj7OKqUB6GDoFDvqyyzNb07AU4xb+GLfHi3fHnhmY=7BjGHA@mail.gmail.com>
Date: Mon, 29 Dec 2025 16:36:25 +0100
From: Benoit Masson <yahoo@...enite.com>
To: Guenter Roeck <linux@...ck-us.net>
Cc: jdelvare@...e.com, linux-hwmon@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] hwmon: it87: describe per-chip temperature resources

On Sun, Dec 28, 2025 at 8:33 PM Guenter Roeck <linux@...ck-us.net> wrote:
> Then why don't you send it as series with this as patch 0 of the series ?
> You are saying this would be to make reviews easier, but in reality you
> are making it more difficult.
>

Hi Guenter,
Thank you for the feedback - you're absolutely right, and I apologize
for the confusing submission approach. My previous reply was probably
too quick and didn't properly address your concerns.
I want to make sure I handle this correctly going forward. Would you
prefer that I:

- Resubmit everything as a proper patch series (0/N with cover letter
explaining the overall goals and how each patch adds support
incrementally), or
- Is there another approach you'd recommend given the current state?

I'm happy to discard the previous 4 patches and start fresh in
whatever format works best for your review process. The goal is to add
support for newer IT87xx variants that many Linux users have in their
systems, and I want to ensure the submission respects both your time
as maintainer and kernel development practices.
I appreciate your guidance on the best path forward.
Best regards,
Benoit