From: Jakub Kicinski <kuba@kernel.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Realtek linux nic maintainers <nic_swsd@realtek.com>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
David Miller <davem@davemloft.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Simon Horman <horms@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 2/2] r8169: add support for reading over-temp threshold
Date: Mon, 6 Jan 2025 15:30:32 -0800 [thread overview]
Message-ID: <20250106153032.7def28fc@kernel.org> (raw)
In-Reply-To: <f3e07026-8219-4b36-b230-7f7ddd71c7ab@gmail.com>
On Mon, 6 Jan 2025 19:05:13 +0100 Heiner Kallweit wrote:
> Add support for reading the over-temp threshold. If the chip temperature
> exceeds this value, the chip will reduce the speed to 1Gbps (by disabling
> 2.5G/5G advertisement and triggering a renegotiation).
If there is a v2 -- please make sure hwmon folks are CCed.
Looks like get_maintainers doesn't flag it, but since we're charting
a new territory for networking a broader audience may be quite useful.
next prev parent reply other threads:[~2025-01-06 23:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 18:00 [PATCH net-next 0/2] r8169: extend hwmon support Heiner Kallweit
2025-01-06 18:01 ` [PATCH net-next 1/2] r8169: prepare for extending " Heiner Kallweit
2025-01-06 21:08 ` Andrew Lunn
2025-01-06 18:05 ` [PATCH net-next 2/2] r8169: add support for reading over-temp threshold Heiner Kallweit
2025-01-06 21:15 ` Andrew Lunn
2025-01-06 22:31 ` Heiner Kallweit
2025-01-06 23:16 ` Andrew Lunn
2025-01-07 7:06 ` Heiner Kallweit
2025-01-06 23:30 ` Jakub Kicinski [this message]
2025-01-07 7:07 ` Heiner Kallweit
2025-01-08 22:13 ` [PATCH net-next 0/2] r8169: extend hwmon support Heiner Kallweit
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=20250106153032.7def28fc@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=pabeni@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).