From: patchwork-bot+netdevbpf@kernel.org
To: Ziyou Xu <xuziyougm@gmail.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, bjorn@mork.no,
ericwouds@gmail.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net v3] net: phy: air_en8811h: restore AN8811HB LED GPIO after MCU restart
Date: Thu, 03 Sep 2026 02:30:15 +0000 [thread overview]
Message-ID: <178840261539.3050934.14870920654715598424.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260829033844.1975-1-xuziyougm@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 29 Aug 2026 11:38:43 +0800 you wrote:
> Commit 03b4702fc5e3 ("net: phy: air_en8811h: move LED GPIO
> configuration to config_init") moved the EN8811H LED GPIO setup from
> probe to config_init because an MD32 restart clears the output-enable
> bits.
>
> AN8811HB follows the same initialization sequence: an8811hb_probe()
> enables GPIO3/4/5, and later config_init() calls restart MD32.
>
> [...]
Here is the summary with links:
- [net,v3] net: phy: air_en8811h: restore AN8811HB LED GPIO after MCU restart
https://git.kernel.org/netdev/net-next/c/3498acda6b68
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-09-03 2:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 3:38 Ziyou Xu
2026-09-03 2:30 ` 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=178840261539.3050934.14870920654715598424.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ericwouds@gmail.com \
--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=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=xuziyougm@gmail.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
all inboxes | Powered by JetHome®