From: patchwork-bot+netdevbpf@kernel.org
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, linux-kernel@vger.kernel.org,
kernel@pengutronix.de, michael.riesch@wolfvision.net,
alexander.stein@ew.tq-group.com
Subject: Re: [PATCH v2] net: phy: dp83867: Add support for hardware blinking LEDs
Date: Fri, 06 Oct 2023 10:40:24 +0000 [thread overview]
Message-ID: <169658882436.10984.4124464343607752178.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231004084026.2214537-1-s.hauer@pengutronix.de>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 4 Oct 2023 10:40:26 +0200 you wrote:
> This implements the led_hw_* hooks to support hardware blinking LEDs on
> the DP83867 phy. The driver supports all LED modes that have a
> corresponding TRIGGER_NETDEV_* define. Error and collision do not have
> a TRIGGER_NETDEV_* define, so these modes are currently not supported.
>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> Tested-by: Alexander Stein <alexander.stein@ew.tq-group.com> #TQMa8MxML/MBa8Mx
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
>
> [...]
Here is the summary with links:
- [v2] net: phy: dp83867: Add support for hardware blinking LEDs
https://git.kernel.org/netdev/net-next/c/1a4890878241
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:[~2023-10-06 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 8:40 [PATCH v2] net: phy: dp83867: Add support for hardware blinking LEDs Sascha Hauer
2023-10-06 10:40 ` 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=169658882436.10984.4124464343607752178.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=andrew@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael.riesch@wolfvision.net \
--cc=netdev@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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).