From: Akhil Goyal <gakhil@marvell.com>
To: Suanming Mou <suanmingm@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH 0/2] crypto/mlx5: optimize AES-GCM IPsec operation
Date: Thu, 13 Jun 2024 18:02:13 +0000 [thread overview]
Message-ID: <CO6PR18MB4484FB97003BCD99D69641F4D8C12@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CO6PR12MB53969840FFFE8FA752683BEEC1C12@CO6PR12MB5396.namprd12.prod.outlook.com>
> Hi Akhil,
>
> Sorry, I just noticed seems you were not added to the list by maintainer script.
> Can you please take a look at the series when available.
>
Please resend. CI is complaining about apply failure.
next prev parent reply other threads:[~2024-06-13 18:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 7:24 Suanming Mou
2024-05-30 7:24 ` [PATCH 1/2] " Suanming Mou
2024-05-30 7:24 ` [PATCH 2/2] crypto/mlx5: add out of place mode for " Suanming Mou
2024-06-13 6:44 ` [PATCH 0/2] crypto/mlx5: optimize AES-GCM " Suanming Mou
2024-06-13 18:02 ` Akhil Goyal [this message]
2024-06-14 0:30 ` Suanming Mou
2024-06-14 0:30 ` [PATCH v2 " Suanming Mou
2024-06-14 0:30 ` [PATCH v2 1/2] " Suanming Mou
2024-06-14 6:49 ` [EXTERNAL] " Akhil Goyal
2024-06-14 7:15 ` Suanming Mou
2024-06-14 9:06 ` Akhil Goyal
2024-06-14 9:32 ` Suanming Mou
2024-06-18 6:47 ` Suanming Mou
2024-06-20 7:40 ` Akhil Goyal
2024-06-20 8:16 ` Suanming Mou
2024-06-20 9:06 ` Akhil Goyal
2024-06-20 9:41 ` Suanming Mou
2024-06-24 8:27 ` Akhil Goyal
2024-06-24 8:41 ` Suanming Mou
2024-06-24 8:44 ` Akhil Goyal
2024-06-24 8:52 ` Suanming Mou
2024-06-14 0:30 ` [PATCH v2 2/2] crypto/mlx5: add out of place mode for " Suanming Mou
2024-06-24 9:16 ` [PATCH v3 0/2] crypto/mlx5: optimize AES-GCM " Suanming Mou
2024-06-24 9:16 ` [PATCH v3 1/2] " Suanming Mou
2024-06-24 9:16 ` [PATCH v3 2/2] crypto/mlx5: add out of place mode for " Suanming Mou
2024-06-26 6:49 ` [EXTERNAL] [PATCH v3 0/2] crypto/mlx5: optimize AES-GCM " Akhil Goyal
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=CO6PR18MB4484FB97003BCD99D69641F4D8C12@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=suanmingm@nvidia.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).