All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Aleksei Sviridkin <f@lex.la>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
	netdev@vger.kernel.org, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, ericwouds@gmail.com,
	lucienzx159@gmail.com, albert-al.lee@airoha.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: phy: air_en8811h: use firmware loaded by the bootloader
Date: Thu, 19 Nov 2026 01:20:05 +0000	[thread overview]
Message-ID: <179505120504.2698221.2135616364374088700.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261112134300.4188612-1-f@lex.la>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 12 Nov 2026 16:43:00 +0300 you wrote:
> On a Keenetic KN-1012 (MT7981) the EN8811H sits behind a port of an
> MT7531 switch. The driver has to be built in there: as a module it loads
> after DSA has validated the port against the generic PHY driver and
> failed to set it up. Built in, it probes when the Ethernet MDIO bus is
> registered, before the root filesystem is mounted, so
> request_firmware_direct() fails with -ENOENT, the PHY stays without a
> driver and the port never comes up, although the bootloader has already
> loaded and started the MD32 firmware.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] net: phy: air_en8811h: use firmware loaded by the bootloader
    https://git.kernel.org/netdev/net-next/c/89f0fb60afdb

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-11-19  1:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 13:43 [PATCH net-next v2] net: phy: air_en8811h: use firmware loaded by the bootloader Aleksei Sviridkin
2026-11-19  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=179505120504.2698221.2135616364374088700.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=albert-al.lee@airoha.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=ericwouds@gmail.com \
    --cc=f@lex.la \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lucienzx159@gmail.com \
    --cc=netdev@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.