From: Krzysztof Kozlowski <krzk@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>,
Roman Gushchin <roman.gushchin@linux.dev>
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: Mon, 20 Apr 2026 13:20:15 +0200 [thread overview]
Message-ID: <8aa0943c-91b5-4a6d-bb2d-d3ac14e59d34@kernel.org> (raw)
In-Reply-To: <cb47e2b5-5da8-472f-9c4e-7414b6cddf84@roeck-us.net>
On 16/04/2026 20:09, Guenter Roeck wrote:
> On Thu, Apr 16, 2026 at 05:45:52PM +0000, Roman Gushchin wrote:
>> 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).
>
> I find it useful. Please don't take it out. Maybe there is a means to drop
> it from devicetree patches if that is what devicetree maintainers want. Fine
> with me to drop it for those, or to drop devicetree feedback entirely if
> that is what devicetree maintainers want and if it is possible to separate
> devicetree patches submitted as part of a hwmon series from the actual code
> patches.
>
If there are folks who want them, then it's fine, don't make exception
just for me. I can skip first paragraphs by default :)
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-20 11:20 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
2026-04-16 18:09 ` Guenter Roeck
2026-04-20 11:20 ` Krzysztof Kozlowski [this message]
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=8aa0943c-91b5-4a6d-bb2d-d3ac14e59d34@kernel.org \
--to=krzk@kernel.org \
--cc=alexisczezar.torreno@analog.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=roman.gushchin@linux.dev \
--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