From: patchwork-bot+netdevbpf@kernel.org
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: andrew@lunn.ch, olteanv@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
chester.a.unal@arinc9.com, daniel@makrotopia.org,
dqfext@gmail.com, sean.wang@mediatek.com,
SkyLake.Huang@mediatek.com, hkallweit1@gmail.com,
linux@armlinux.org.uk, arinc.unal@arinc9.com,
Landen.Chao@mediatek.com, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [net-next PATCH 0/3] net: dsa: mt7530: Add AN7583 support + PHY
Date: Wed, 28 May 2025 01:20:42 +0000 [thread overview]
Message-ID: <174839524201.1849945.3988099260497875532.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250522165313.6411-1-ansuelsmth@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 22 May 2025 18:53:08 +0200 you wrote:
> This small series add the required changes to make Airoha AN7583
> Switch and Internal PHY work due to strange default configuration.
>
> Christian Marangi (3):
> dt-bindings: net: dsa: mediatek,mt7530: Add airoha,an7583-switch
> net: dsa: mt7530: Add AN7583 support
> net: phy: mediatek: Add Airoha AN7583 PHY support
>
> [...]
Here is the summary with links:
- [net-next,1/3] dt-bindings: net: dsa: mediatek,mt7530: Add airoha,an7583-switch
https://git.kernel.org/netdev/net-next/c/fef184880923
- [net-next,2/3] net: dsa: mt7530: Add AN7583 support
https://git.kernel.org/netdev/net-next/c/d76556db10bf
- [net-next,3/3] net: phy: mediatek: Add Airoha AN7583 PHY support
https://git.kernel.org/netdev/net-next/c/8bc3c234dcb6
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:[~2025-05-28 1:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 16:53 [net-next PATCH 0/3] net: dsa: mt7530: Add AN7583 support + PHY Christian Marangi
2025-05-22 16:53 ` [net-next PATCH 1/3] dt-bindings: net: dsa: mediatek,mt7530: Add airoha,an7583-switch Christian Marangi
2025-05-23 15:34 ` Conor Dooley
2025-05-22 16:53 ` [net-next PATCH 2/3] net: dsa: mt7530: Add AN7583 support Christian Marangi
2025-05-23 16:00 ` Andrew Lunn
2025-05-22 16:53 ` [net-next PATCH 3/3] net: phy: mediatek: Add Airoha AN7583 PHY support Christian Marangi
2025-05-23 15:58 ` Andrew Lunn
2025-05-28 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=174839524201.1849945.3988099260497875532.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Landen.Chao@mediatek.com \
--cc=SkyLake.Huang@mediatek.com \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ansuelsmth@gmail.com \
--cc=arinc.unal@arinc9.com \
--cc=chester.a.unal@arinc9.com \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=sean.wang@mediatek.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;
as well as URLs for NNTP newsgroup(s).