From: patchwork-bot+netdevbpf@kernel.org
To: Subbaraya Sundeep <sbhatta@marvell.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
sd@queasysnail.net, gakula@marvell.com, hkelam@marvell.com,
sgoutham@marvell.com, lcherian@marvell.com,
bbhushan2@marvell.com, jerinj@marvell.com,
netdev@vger.kernel.org
Subject: Re: [net-next PATCH v3 0/2] octeontx2-pf: Do not detect MACSEC block based on silicon
Date: Tue, 27 May 2025 10:00:32 +0000 [thread overview]
Message-ID: <174834003201.1237935.7363825468399799478.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1747894516-4565-1-git-send-email-sbhatta@marvell.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 22 May 2025 11:45:16 +0530 you wrote:
> Out of various silicon variants of CN10K series some have hardware
> MACSEC block for offloading MACSEC operations and some do not.
> AF driver already has the information of whether MACSEC is present
> or not on running silicon. Hence fetch that information from
> AF via mailbox message.
>
> Changes for v3:
> None. Resubmitting as v3 since there is no activity on v2
> for a while.
> Changes for v2:
> Changed subject prefix to net-next
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] octeontx2-af: Add MACSEC capability flag
https://git.kernel.org/netdev/net-next/c/732038370e55
- [net-next,v3,2/2] octeontx2-pf: macsec: Get MACSEC capability flag from AF
https://git.kernel.org/netdev/net-next/c/5fa6f0245960
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-27 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 6:15 [net-next PATCH v3 0/2] octeontx2-pf: Do not detect MACSEC block based on silicon Subbaraya Sundeep
2025-05-27 10:00 ` 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=174834003201.1237935.7363825468399799478.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=horms@kernel.org \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sd@queasysnail.net \
--cc=sgoutham@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.