From: patchwork-bot+netdevbpf@kernel.org
To: Andrei Botila <andrei.botila@oss.nxp.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, s32@nxp.com, clizzi@redhat.com,
aruizrui@redhat.com, eballetb@redhat.com
Subject: Re: [PATCH net-next v2 0/2] net: phy: nxp-c45-tja11xx: add support for TJA1121
Date: Wed, 05 Mar 2025 01:20:40 +0000 [thread overview]
Message-ID: <174113764050.356990.3050200111085365446.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250228154320.2979000-1-andrei.botila@oss.nxp.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 28 Feb 2025 17:43:18 +0200 you wrote:
> This patch series adds .match_phy_device for the existing TJAs
> to differentiate between TJA1103/TJA1104 and TJA1120/TJA1121.
> TJA1103 and TJA1104 share the same PHY_ID but TJA1104 has MACsec
> capabilities while TJA1103 doesn't.
> Also add support for TJA1121 which is based on TJA1120 hardware
> with additional MACsec IP.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: phy: nxp-c45-tja11xx: add match_phy_device to TJA1103/TJA1104
https://git.kernel.org/netdev/net-next/c/a06a868a0cd9
- [net-next,v2,2/2] net: phy: nxp-c45-tja11xx: add support for TJA1121
https://git.kernel.org/netdev/net-next/c/7215e9375694
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-03-05 1:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 15:43 [PATCH net-next v2 0/2] net: phy: nxp-c45-tja11xx: add support for TJA1121 Andrei Botila
2025-02-28 15:43 ` [PATCH net-next v2 1/2] net: phy: nxp-c45-tja11xx: add match_phy_device to TJA1103/TJA1104 Andrei Botila
2025-02-28 16:40 ` Andrew Lunn
2025-02-28 15:43 ` [PATCH net-next v2 2/2] net: phy: nxp-c45-tja11xx: add support for TJA1121 Andrei Botila
2025-02-28 16:41 ` Andrew Lunn
2025-03-05 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=174113764050.356990.3050200111085365446.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrei.botila@oss.nxp.com \
--cc=andrew@lunn.ch \
--cc=aruizrui@redhat.com \
--cc=clizzi@redhat.com \
--cc=davem@davemloft.net \
--cc=eballetb@redhat.com \
--cc=edumazet@google.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=s32@nxp.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