From: "Rob Herring (Arm)" <robh@kernel.org>
To: Igor Velkov <iav@iav.lv>
Cc: Heiko Stuebner <heiko@sntech.de>,
linux-hwmon@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Jean Delvare <jdelvare@suse.com>,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Guenter Roeck <linux@roeck-us.net>,
linux-arm-kernel@lists.infradead.org,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: hwmon: pwm-fan: Reference the common fan schema
Date: Fri, 30 Oct 2026 10:38:39 -0500 [thread overview]
Message-ID: <179337471871.91953.13659250524662558962.robh@kernel.org> (raw)
In-Reply-To: <20261018-helios64-fan-label-v1-1-69a3f96d4efa@iav.lv>
On Sun, 18 Oct 2026 07:54:59 +0300, Igor Velkov wrote:
> pwm-fan predates fan-common.yaml and repeats several of its properties.
> Reference the common schema, drop the duplicated properties and keep
> only the constraints specific to PWM fans.
>
> This also allows label, which the hwmon core exposes as the label
> attribute.
>
> Link: https://lore.kernel.org/r/20250106173805.GA501301-robh@kernel.org
> Assisted-by: LLM
> Signed-off-by: Igor Velkov <iav@iav.lv>
> ---
> .../devicetree/bindings/hwmon/pwm-fan.yaml | 22 +++++-----------------
> 1 file changed, 5 insertions(+), 17 deletions(-)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-10-30 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 4:54 [PATCH 0/2] Label the fans on Kobol Helios64 Igor Velkov via B4 Relay
2026-10-18 4:54 ` [PATCH 1/2] dt-bindings: hwmon: pwm-fan: Reference the common fan schema Igor Velkov via B4 Relay
2026-10-30 15:38 ` Rob Herring (Arm) [this message]
2026-10-30 19:52 ` Guenter Roeck
2026-10-18 4:55 ` [PATCH 2/2] arm64: dts: rockchip: Label the fans on Kobol Helios64 Igor Velkov via B4 Relay
2026-11-01 22:16 ` (subset) [PATCH 0/2] " Heiko Stuebner
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=179337471871.91953.13659250524662558962.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=iav@iav.lv \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@roeck-us.net \
/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®