From: Andrew Lunn <andrew@lunn.ch>
To: me@marleb.org
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 3/3] net: phy: realtek: register hwmon thermal zones
Date: Sat, 7 Nov 2026 18:22:36 +0100 [thread overview]
Message-ID: <ed20a09c-e275-4124-90b7-8b1ada9fbf91@lunn.ch> (raw)
In-Reply-To: <20261107-realtek-hwmon-tz-v2-3-6b9a69d44470@marleb.org>
> I tested this on a Zyxel XGS1250-12 B1 with OpenWrt's Linux 6.18.55,
> where OpenWrt's out-of-tree RTL8261N support calls
> rtl822x_hwmon_init():
Mainline does not care about out of tree code.
Does this have any value for Mainline?
If not, drop it.
Or bring the out of tree code into Mainline.
Andrew
next prev parent reply other threads:[~2026-11-07 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 17:00 [PATCH net-next v2 0/3] " Hleb Shauchenka via B4 Relay
2026-11-07 17:00 ` [PATCH net-next v2 1/3] dt-bindings: net: ethernet-phy: add property #thermal-sensor-cells Hleb Shauchenka via B4 Relay
2026-11-07 17:15 ` Andrew Lunn
2026-11-07 17:00 ` [PATCH net-next v2 2/3] net: phy: realtek: return MDIO read errors from hwmon Hleb Shauchenka via B4 Relay
2026-11-07 17:18 ` Andrew Lunn
2026-11-07 17:00 ` [PATCH net-next v2 3/3] net: phy: realtek: register hwmon thermal zones Hleb Shauchenka via B4 Relay
2026-11-07 17:22 ` Andrew Lunn [this message]
2026-11-07 17:58 ` Hleb Shauchenka
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=ed20a09c-e275-4124-90b7-8b1ada9fbf91@lunn.ch \
--to=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=me@marleb.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.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®