public inbox for linux-hwmon@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Gushchin <roman.gushchin@linux.dev>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: sashiko@lists.linux.dev,
	 Alexis Czezar Torreno <alexisczezar.torreno@analog.com>,
	 linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: hwmon: pmbus: add max20830
Date: Thu, 16 Apr 2026 17:45:52 +0000	[thread overview]
Message-ID: <7ia4mrz2ssrz.fsf@castle.c.googlers.com> (raw)
In-Reply-To: <20260416-winged-ivory-mandrill-f1e8b3@quoll> (Krzysztof Kozlowski's message of "Thu, 16 Apr 2026 11:25:26 +0200")

Krzysztof Kozlowski <krzk@kernel.org> writes:

> On Tue, Apr 14, 2026 at 04:38:40AM +0000, sashiko-bot@kernel.org wrote:
>> Sashiko AI review found 3 potential issue(s):
>> - [Medium] Incomplete Regulator Schema
>> - [Medium] Missing Hardware Capability (Interrupts)
>> - [Low] Devicetree Best Practices Violation (Node Name)
>> --
>> 
>> commit 20a4d8dcd2f3344ac22d7d2e974bae1ef57874ed
>> Author: Alexis Czezar Torreno <alexisczezar.torreno@analog.com>
>> 
>> dt-bindings: hwmon: pmbus: add max20830
>> 
>> This commit adds device tree documentation for the MAX20830 step-down DC-DC
>> switching regulator with PMBus interface. It allows monitoring of voltage,
>> current, and temperature.
>
> Sashiko devs,
> Can we drop such comments? They are useless - we know what the commit is
> doing, no point for reviewing tool to say it again.

It's the format which originated from initial Chris Mason's prompts
and as *I understand* it's purpose was to make sure the llm is reviewing
the right patch and more or less understands it. Idk if we still need
this, but at least some find it useful: e.g.
https://github.com/sashiko-dev/sashiko/issues/90 .

I'm planning to do it configurable in UI, but for emails I can
only make it configurable on per-subsystem basis.
If there is a consensus amongst hwmon maintainers, I'm happy to remove
it for hwmon (in several days).

>
> Please send only useful feedback to mailing list, otherwise this will be
> just noise and going to be ignored.

Agree, but there are many sometimes conflicting opinions on what's
useful and what's not. So I'm trying to make it as flexible and
configurable as possible.

Thanks

  reply	other threads:[~2026-04-16 17:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14  4:28 [PATCH 0/2] Add support for MAX20830 PMBUS Alexis Czezar Torreno
2026-04-14  4:28 ` [PATCH 1/2] dt-bindings: hwmon: pmbus: add max20830 Alexis Czezar Torreno
2026-04-14  4:38   ` sashiko-bot
2026-04-16  9:25     ` Krzysztof Kozlowski
2026-04-16 17:45       ` Roman Gushchin [this message]
2026-04-16 18:09         ` Guenter Roeck
2026-04-20 11:20           ` Krzysztof Kozlowski
2026-04-14  4:28 ` [PATCH 2/2] hwmon: (pmbus/max20830) add driver for max20830 Alexis Czezar Torreno
2026-04-14  4:56   ` sashiko-bot
2026-04-14 14:54     ` Guenter Roeck
2026-04-15  2:21       ` Torreno, Alexis Czezar
2026-04-15  3:02         ` Guenter Roeck
2026-04-15  4:27           ` Torreno, Alexis Czezar
2026-04-16  3:04           ` Torreno, Alexis Czezar
2026-04-16  4:49             ` 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=7ia4mrz2ssrz.fsf@castle.c.googlers.com \
    --to=roman.gushchin@linux.dev \
    --cc=alexisczezar.torreno@analog.com \
    --cc=krzk@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=sashiko@lists.linux.dev \
    /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