From: patchwork-bot+netdevbpf@kernel.org
To: Konstantin Meshkov <skyline@mail.ru>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, kuba@kernel.org, pabeni@redhat.com,
edumazet@kernel.org, olek2@wp.pl, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: phy: marvell: add LED support for 88E1116R PHY
Date: Fri, 16 Oct 2026 01:20:04 +0000 [thread overview]
Message-ID: <179211360427.4193708.3061340075824746062.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <179165733751.2921261.13784246298385245617@mail.ru>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 10 Oct 2026 21:35:37 +0300 you wrote:
> The Marvell 88E1116R PHY (used on the D-Link DNS-325) exposes its LEDs
> through the same page 3 register 0x10 LED control layout as the 88E1318S.
> Wire up the existing 88E1318S LED handlers in the 88E1116R driver entry
> so the PHY LEDs can be described in the device tree and driven through
> the LED trigger API with hardware offload.
>
> Tested on a D-Link DNS-325 (88E1116R): both PHY LEDs are registered and
> hardware-offloaded.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: phy: marvell: add LED support for 88E1116R PHY
https://git.kernel.org/netdev/net-next/c/ce7db1caaa68
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-16 1:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 18:35 [PATCH net-next v2] net: phy: marvell: add LED support for 88E1116R PHY Konstantin Meshkov
2026-10-11 13:30 ` Andrew Lunn
2026-10-13 2:38 ` Andrew Lunn
2026-10-16 1:20 ` patchwork-bot+netdevbpf [this message]
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=179211360427.4193708.3061340075824746062.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=edumazet@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olek2@wp.pl \
--cc=pabeni@redhat.com \
--cc=skyline@mail.ru \
/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