From: Zhen Yit Chong <czy331@gmail.com>
To: anoobj@marvell.com
Cc: adwivedi@marvell.com, dev@dpdk.org, gakhil@marvell.com,
jerinj@marvell.com, ktejasree@marvell.com, schalla@marvell.com,
thomas@monjalon.net
Subject: Re: [dpdk-dev] [PATCH v3 4/8] crypto/cnxk: add security capabilities
Date: Fri, 6 Jun 2025 19:15:56 +0800 [thread overview]
Message-ID: <CAFYAXgbM74G5Q0vgeZuUuTo3t5Sz=-9cz3hhRJbySpoOr0UpOg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: Type: text/html, Size: 23 bytes --]
next reply other threads:[~2025-06-08 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 11:15 Zhen Yit Chong [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-25 6:15 [dpdk-dev] [PATCH v2 0/4] Add rte_security in crypto_cn10k PMD Anoob Joseph
2021-06-29 7:34 ` [dpdk-dev] [PATCH v3 0/8] Add lookaside IPsec and asymmetric in cnxk crypto PMDs Anoob Joseph
2021-06-29 7:34 ` [dpdk-dev] [PATCH v3 4/8] crypto/cnxk: add security capabilities Anoob Joseph
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='CAFYAXgbM74G5Q0vgeZuUuTo3t5Sz=-9cz3hhRJbySpoOr0UpOg@mail.gmail.com' \
--to=czy331@gmail.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=ktejasree@marvell.com \
--cc=schalla@marvell.com \
--cc=thomas@monjalon.net \
/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).