From: Subbaraya Sundeep <sbhatta@marvell.com>
To: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<horms@kernel.org>, <gakula@marvell.com>, <hkelam@marvell.com>,
<sgoutham@marvell.com>, <lcherian@marvell.com>,
<bbhushan2@marvell.com>, <jerinj@marvell.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: [net PATCH 0/2] octeontx2-pf: Do not detect MACSEC block based on silicon
Date: Sun, 11 May 2025 13:15:12 +0000 [thread overview]
Message-ID: <aCCi4JcJtzh1bfP-@effaecf3b85e> (raw)
In-Reply-To: <1746938403-6667-1-git-send-email-sbhatta@marvell.com>
Hi,
Please igonre this series. Wrong prefix in subject. Will correct and
send v2.
Thanks,
Sundeep
On 2025-05-11 at 04:40:01, Subbaraya Sundeep (sbhatta@marvell.com) 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.
>
> Subbaraya Sundeep (2):
> octeontx2-af: Add MACSEC capability flag
> octeontx2-pf: macsec: Get MACSEC capability flag from AF
>
> drivers/net/ethernet/marvell/octeontx2/af/mbox.h | 2 ++
> drivers/net/ethernet/marvell/octeontx2/af/rvu.c | 3 ++
> .../ethernet/marvell/octeontx2/nic/otx2_common.c | 37 ++++++++++++++++++++++
> .../ethernet/marvell/octeontx2/nic/otx2_common.h | 4 +--
> .../net/ethernet/marvell/octeontx2/nic/otx2_pf.c | 2 ++
> 5 files changed, 45 insertions(+), 3 deletions(-)
>
> --
> 2.7.4
>
prev parent reply other threads:[~2025-05-11 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-11 4:40 [net PATCH 0/2] octeontx2-pf: Do not detect MACSEC block based on silicon Subbaraya Sundeep
2025-05-11 4:40 ` [net PATCH 1/2] octeontx2-af: Add MACSEC capability flag Subbaraya Sundeep
2025-05-11 4:40 ` [net PATCH 2/2] octeontx2-pf: macsec: Get MACSEC capability flag from AF Subbaraya Sundeep
2025-05-11 13:15 ` Subbaraya Sundeep [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=aCCi4JcJtzh1bfP-@effaecf3b85e \
--to=sbhatta@marvell.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox