From: patchwork-bot+netdevbpf@kernel.org
To: Linus Walleij <linus.walleij@linaro.org>
Cc: opendmb@gmail.com, florian.fainelli@broadcom.com,
bcm-kernel-feedback-list@broadcom.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
rafal@milecki.pl, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, f.fainelli@gmail.com,
netdev@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/2] net: phy: mdio-bcm-unimac: Add BCM6846 variant
Date: Wed, 16 Oct 2024 01:30:29 +0000 [thread overview]
Message-ID: <172904222974.1350766.8131356832857908071.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241012-bcm6846-mdio-v1-0-c703ca83e962@linaro.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 12 Oct 2024 22:35:21 +0200 you wrote:
> As pointed out by Florian:
> https://lore.kernel.org/linux-devicetree/b542b2e8-115c-4234-a464-e73aa6bece5c@broadcom.com/
>
> The BCM6846 has a few extra registers and cannot reuse the
> compatible string from other variants of the Unimac
> MDIO block: we need to be able to tell them apart.
>
> [...]
Here is the summary with links:
- [1/2] dt-bindings: net: brcm,unimac-mdio: Add bcm6846-mdio
https://git.kernel.org/netdev/net/c/6ed97afd75cc
- [2/2] net: phy: mdio-bcm-unimac: Add BCM6846 support
https://git.kernel.org/netdev/net/c/906b77ca91c7
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:[~2024-10-16 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 20:35 [PATCH 0/2] net: phy: mdio-bcm-unimac: Add BCM6846 variant Linus Walleij
2024-10-12 20:35 ` [PATCH 1/2] dt-bindings: net: brcm,unimac-mdio: Add bcm6846-mdio Linus Walleij
2024-10-15 19:56 ` Rob Herring (Arm)
2024-10-12 20:35 ` [PATCH 2/2] net: phy: mdio-bcm-unimac: Add BCM6846 support Linus Walleij
2024-10-16 1: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=172904222974.1350766.8131356832857908071.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--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=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.com \
--cc=pabeni@redhat.com \
--cc=rafal@milecki.pl \
--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;
as well as URLs for NNTP newsgroup(s).