From: "Kamil Horák (2N)" <kamilh@axis.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: florian.fainelli@broadcom.com,
bcm-kernel-feedback-list@broadcom.com, andrew@lunn.ch,
hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, krzk+dt@kernel.org,
conor+dt@kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
f.fainelli@gmail.com, robh@kernel.org, andrew+netdev@lunn.ch,
horms@kernel.org, corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [PATCH net v6 0/4] net: phy: bcm54811: Fix the PHY initialization
Date: Tue, 8 Jul 2025 11:01:29 +0200 [thread overview]
Message-ID: <727872e9-6043-4dec-9ea5-4523d9c08f18@axis.com> (raw)
In-Reply-To: <20250707125335.213ed1d7@kernel.org>
On 7/7/25 21:53, Jakub Kicinski wrote:
> On Fri, 4 Jul 2025 10:35:08 +0200 Kamil Horák - 2N wrote:
>> Fix the bcm54811 PHY driver initialization for MII-Lite.
>
> Sorry for the delay, I went AFK for the long weekend shortly after
> responding to v5. IIUC bcm54811 basically never worked, so I think
> net-next is appropriate for the whole series. Please rebase and strip
> the Fixes tags.
OK tried to do so as best as possible. Keeping the Reviewed tags, hope
it is correct even when we switched to net-next.
The PHY still initializes and runs correctly in the kernel built from
net-next.
Kamil
prev parent reply other threads:[~2025-07-08 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 8:35 Kamil Horák - 2N
2025-07-04 8:35 ` [PATCH net v6 1/4] net: phy: MII-Lite PHY interface mode Kamil Horák - 2N
2025-07-04 8:35 ` [PATCH net v6 2/4] dt-bindings: ethernet-phy: add MII-Lite phy interface type Kamil Horák - 2N
2025-07-04 8:35 ` [PATCH net v6 3/4] net: phy: bcm5481x: MII-Lite activation Kamil Horák - 2N
2025-07-04 8:35 ` [PATCH net v6 4/4] net: phy: bcm54811: Fix the PHY initialization Kamil Horák - 2N
2025-07-07 19:53 ` [PATCH net v6 0/4] " Jakub Kicinski
2025-07-08 9:01 ` Kamil Horák (2N) [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=727872e9-6043-4dec-9ea5-4523d9c08f18@axis.com \
--to=kamilh@axis.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
/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®