From: patchwork-bot+netdevbpf@kernel.org
To: Radu Pirea (NXP OSS) <radu-nicolae.pirea@oss.nxp.com>
Cc: sd@queasysnail.net, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, andrew@lunn.ch,
hkallweit1@gmail.com, linux@armlinux.org.uk,
richardcochran@gmail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, sebastian.tobuschat@oss.nxp.com,
andrei.botila@oss.nxp.com
Subject: Re: [PATCH net-next v9 0/9] Add MACsec support for TJA11XX C45 PHYs
Date: Wed, 27 Dec 2023 13:10:25 +0000 [thread overview]
Message-ID: <170368262541.3726.479057551410543516.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231219145333.240323-1-radu-nicolae.pirea@oss.nxp.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 19 Dec 2023 16:53:24 +0200 you wrote:
> This is the MACsec support for TJA11XX PHYs. The MACsec block encrypts
> the ethernet frames on the fly and has no buffering. This operation will
> grow the frames by 32 bytes. If the frames are sent back to back, the
> MACsec block will not have enough room to insert the SecTAG and the ICV
> and the frames will be dropped.
>
> To mitigate this, the PHY can parse a specific ethertype with some
> padding bytes and replace them with the SecTAG and ICV. These padding
> bytes might be dummy or might contain information about TX SC that must
> be used to encrypt the frame.
>
> [...]
Here is the summary with links:
- [net-next,v9,1/9] net: rename dsa_realloc_skb to skb_ensure_writable_head_tail
https://git.kernel.org/netdev/net-next/c/90abde49ea85
- [net-next,v9,2/9] net: macsec: use skb_ensure_writable_head_tail to expand the skb
https://git.kernel.org/netdev/net-next/c/b34ab3527b96
- [net-next,v9,3/9] net: macsec: move sci_to_cpu to macsec header
https://git.kernel.org/netdev/net-next/c/b1c036e835b6
- [net-next,v9,4/9] net: macsec: documentation for macsec_context and macsec_ops
https://git.kernel.org/netdev/net-next/c/eb97b9bd38f9
- [net-next,v9,5/9] net: macsec: revert the MAC address if mdo_upd_secy fails
https://git.kernel.org/netdev/net-next/c/25a00d0cd691
- [net-next,v9,6/9] net: macsec: introduce mdo_insert_tx_tag
https://git.kernel.org/netdev/net-next/c/a73d8779d61a
- [net-next,v9,7/9] net: phy: nxp-c45-tja11xx: add MACsec support
https://git.kernel.org/netdev/net-next/c/a868b486cb88
- [net-next,v9,8/9] net: phy: nxp-c45-tja11xx: add MACsec statistics
https://git.kernel.org/netdev/net-next/c/31a99fc06b0b
- [net-next,v9,9/9] net: phy: nxp-c45-tja11xx: implement mdo_insert_tx_tag
https://git.kernel.org/netdev/net-next/c/dc1a00380aa6
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:[~2023-12-27 13:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 14:53 [PATCH net-next v9 0/9] Add MACsec support for TJA11XX C45 PHYs Radu Pirea (NXP OSS)
2023-12-19 14:53 ` [PATCH net-next v9 1/9] net: rename dsa_realloc_skb to skb_ensure_writable_head_tail Radu Pirea (NXP OSS)
2023-12-19 14:53 ` [PATCH net-next v9 2/9] net: macsec: use skb_ensure_writable_head_tail to expand the skb Radu Pirea (NXP OSS)
2023-12-19 14:53 ` [PATCH net-next v9 3/9] net: macsec: move sci_to_cpu to macsec header Radu Pirea (NXP OSS)
2023-12-19 14:53 ` [PATCH net-next v9 4/9] net: macsec: documentation for macsec_context and macsec_ops Radu Pirea (NXP OSS)
2023-12-19 14:53 ` [PATCH net-next v9 5/9] net: macsec: revert the MAC address if mdo_upd_secy fails Radu Pirea (NXP OSS)
2023-12-19 14:53 ` [PATCH net-next v9 6/9] net: macsec: introduce mdo_insert_tx_tag Radu Pirea (NXP OSS)
2023-12-19 14:53 ` [PATCH net-next v9 7/9] net: phy: nxp-c45-tja11xx: add MACsec support Radu Pirea (NXP OSS)
2023-12-19 14:53 ` [PATCH net-next v9 8/9] net: phy: nxp-c45-tja11xx: add MACsec statistics Radu Pirea (NXP OSS)
2023-12-19 14:53 ` [PATCH net-next v9 9/9] net: phy: nxp-c45-tja11xx: implement mdo_insert_tx_tag Radu Pirea (NXP OSS)
2023-12-27 13:10 ` 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=170368262541.3726.479057551410543516.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrei.botila@oss.nxp.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--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=radu-nicolae.pirea@oss.nxp.com \
--cc=richardcochran@gmail.com \
--cc=sd@queasysnail.net \
--cc=sebastian.tobuschat@oss.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