From: Akhil Goyal <gakhil@marvell.com>
To: Gagandeep Singh <g.singh@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>
Subject: RE: [EXTERNAL] [PATCH v2 0/9] DPAA2 crypto driver changes
Date: Wed, 21 May 2025 11:59:30 +0000 [thread overview]
Message-ID: <CO6PR18MB4484957133F63EF2E58F9169D89EA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250521065658.857707-1-g.singh@nxp.com>
> V2 changes:
> - fix checkpatch warning
> - fix 32 bit compilation error
> - fix a commit message
> - update document
>
> Gagandeep Singh (5):
> common/dpaax: fix invalid key command error
> common/dpaax: fix for PDCP AES only 12bit SN case
> common/dpaax: support 12bit SN in pdcp uplane
> crypto/dpaa2_sec: change custom device API to standard
> crypto/dpaa2_sec: add null algo capability
>
> Jun Yang (3):
> net/dpaa2: configure buffer layout
> mempool/dpaa2: mempool operation index
> crypto/dpaa2_sec: add support for simple IPsec FD
>
> Vanshika Shukla (1):
> crypto/dpaa2_sec: fix coverity Issues
Split the patchset for appropriate trees. There are patches for net and mempool which will not go in crypto tree. And I don't see them as dependent patches for crypto.
>
> doc/guides/cryptodevs/dpaa2_sec.rst | 2 +
> doc/guides/cryptodevs/features/dpaa2_sec.ini | 2 +
> drivers/bus/fslmc/portal/dpaa2_hw_pvt.h | 10 +
> drivers/common/dpaax/caamflib/desc/pdcp.h | 31 +++-
> drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c | 182 ++++++++++++-------
> drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h | 45 ++++-
> drivers/crypto/dpaa2_sec/meson.build | 3 +-
> drivers/crypto/dpaa_sec/dpaa_sec.c | 42 ++---
> drivers/mempool/dpaa2/dpaa2_hw_mempool.c | 20 +-
> drivers/mempool/dpaa2/dpaa2_hw_mempool.h | 5 +-
> drivers/net/dpaa2/base/dpaa2_hw_dpni.c | 18 +-
> drivers/net/dpaa2/base/dpaa2_hw_dpni_annot.h | 6 +
> drivers/net/dpaa2/dpaa2_ethdev.h | 6 +-
> 13 files changed, 263 insertions(+), 109 deletions(-)
>
> --
> 2.25.1
prev parent reply other threads:[~2025-05-21 11:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 5:51 [PATCH 1/9] common/dpaax: fix invalid key command error Gagandeep Singh
2025-05-20 5:51 ` [PATCH 2/9] common/dpaax: fix for PDCP AES only 12bit SN case Gagandeep Singh
2025-05-20 5:51 ` [PATCH 3/9] common/dpaax: support 12bit SN in pdcp uplane Gagandeep Singh
2025-05-20 6:18 ` Hemant Agrawal
2025-05-21 4:50 ` Gagandeep Singh
2025-05-20 5:51 ` [PATCH 4/9] crypto/dpaa2_sec: change custom device API to standard Gagandeep Singh
2025-05-20 5:51 ` [PATCH 5/9] crypto/dpaa2_sec: fix coverity Issues Gagandeep Singh
2025-05-20 5:51 ` [PATCH 6/9] crypto/dpaa2_sec: add null algo capability Gagandeep Singh
2025-05-20 6:20 ` Hemant Agrawal
2025-05-21 4:51 ` Gagandeep Singh
2025-05-20 5:51 ` [PATCH 7/9] net/dpaa2: configure buffer layout Gagandeep Singh
2025-05-20 5:51 ` [PATCH 8/9] mempool/dpaa2: mempool operation index Gagandeep Singh
2025-05-20 5:51 ` [PATCH 9/9] crypto/dpaa2_sec: add support for simple IPsec FD Gagandeep Singh
2025-05-20 6:16 ` [PATCH 1/9] common/dpaax: fix invalid key command error Hemant Agrawal
2025-05-21 4:43 ` Gagandeep Singh
2025-05-21 6:56 ` [PATCH v2 0/9] DPAA2 crypto driver changes Gagandeep Singh
2025-05-21 6:56 ` [PATCH v2 1/9] common/dpaax: fix invalid key command error Gagandeep Singh
2025-05-21 6:56 ` [PATCH v2 2/9] common/dpaax: fix for PDCP AES only 12bit SN case Gagandeep Singh
2025-05-21 6:56 ` [PATCH v2 3/9] common/dpaax: support 12bit SN in pdcp uplane Gagandeep Singh
2025-05-21 6:56 ` [PATCH v2 4/9] crypto/dpaa2_sec: change custom device API to standard Gagandeep Singh
2025-05-21 6:56 ` [PATCH v2 5/9] crypto/dpaa2_sec: fix coverity Issues Gagandeep Singh
2025-05-21 6:56 ` [PATCH v2 6/9] crypto/dpaa2_sec: add null algo capability Gagandeep Singh
2025-05-21 6:56 ` [PATCH v2 7/9] net/dpaa2: configure buffer layout Gagandeep Singh
2025-05-21 6:56 ` [PATCH v2 8/9] mempool/dpaa2: mempool operation index Gagandeep Singh
2025-05-21 6:56 ` [PATCH v2 9/9] crypto/dpaa2_sec: add support for simple IPsec FD Gagandeep Singh
2025-05-21 11:59 ` Akhil Goyal [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=CO6PR18MB4484957133F63EF2E58F9169D89EA@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@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;
as well as URLs for NNTP newsgroup(s).