From: Guenter Roeck <linux@roeck-us.net>
To: Robert Marko <robert.marko@sartura.hr>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
corbet@lwn.net, skhan@linuxfoundation.org, rdunlap@infradead.org,
nicolas.ferre@microchip.com, claudiu.beznea@tuxon.dev,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, luka.perkov@sartura.hr
Subject: Re: [PATCH v3 3/4] hwmon: Add Microchip LAN969x fan controller driver
Date: Sat, 14 Nov 2026 08:48:11 -0800 [thread overview]
Message-ID: <118d242e-6511-4374-acde-80efbe7bbc34@roeck-us.net> (raw)
In-Reply-To: <20261111161619.232141-3-robert.marko@sartura.hr>
On Wed, Nov 11, 2026 at 05:12:47PM +0100, Robert Marko wrote:
> The LAN969x fan controller has its own register block, separate
> from the Sparx5-compatible temperature sensor.
>
> Add a dedicated hwmon driver for tachometer, PWM, and thermal cooling.
>
> Signed-off-by: Robert Marko <robert.marko@sartura.hr>
Applied.
Thanks,
Guenter
next prev parent reply other threads:[~2026-11-14 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 16:12 [PATCH v3 1/4] dt-bindings: hwmon: fan-common: reject zero pulses per revolution Robert Marko
2026-11-11 16:12 ` [PATCH v3 2/4] dt-bindings: hwmon: add Microchip LAN969x fan controller Robert Marko
2026-11-12 1:06 ` Rob Herring (Arm)
2026-11-14 16:44 ` Guenter Roeck
2026-11-11 16:12 ` [PATCH v3 3/4] hwmon: Add Microchip LAN969x fan controller driver Robert Marko
2026-11-14 16:48 ` Guenter Roeck [this message]
2026-11-11 16:12 ` [PATCH v3 4/4] arm64: dts: microchip: lan969x: add fan controller Robert Marko
2026-11-12 1:05 ` [PATCH v3 1/4] dt-bindings: hwmon: fan-common: reject zero pulses per revolution Rob Herring
2026-11-14 16:43 ` 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=118d242e-6511-4374-acde-80efbe7bbc34@roeck-us.net \
--to=linux@roeck-us.net \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luka.perkov@sartura.hr \
--cc=nicolas.ferre@microchip.com \
--cc=rdunlap@infradead.org \
--cc=robert.marko@sartura.hr \
--cc=robh@kernel.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
all inboxes | Powered by JetHome®