From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Brian Dooley <brian.dooley@intel.com>, Kai Ji <kai.ji@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org, gakhil@marvell.com
Subject: Re: [PATCH v3 1/2] crypto/ipsec_mb: remove unused defines
Date: Fri, 7 Jul 2023 13:38:15 +0200 [thread overview]
Message-ID: <7db1bcbd-2e7b-6b32-cade-23958448c4be@redhat.com> (raw)
In-Reply-To: <20230706162117.481960-2-brian.dooley@intel.com>
On 7/6/23 18:21, Brian Dooley wrote:
> removed AESNI_MB_DOCSIS_SEC_ENABLED defines as they are no longer used.
>
> Fixes: 798f9d134519 ("crypto/ipsec_mb: remove security lib presence checks")
> Cc: maxime.coquelin@redhat.com
>
> Signed-off-by: Brian Dooley <brian.dooley@intel.com>
> ---
> drivers/crypto/ipsec_mb/ipsec_mb_private.c | 4 ----
> drivers/crypto/ipsec_mb/pmd_aesni_mb.c | 22 ++-------------------
> drivers/crypto/ipsec_mb/pmd_aesni_mb_priv.h | 1 -
> 3 files changed, 2 insertions(+), 25 deletions(-)
>
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
next prev parent reply other threads:[~2023-07-07 11:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 13:15 [PATCH v1] " Brian Dooley
2023-07-06 16:04 ` [PATCH v2 0/2] " Brian Dooley
2023-07-06 16:04 ` [PATCH v2 1/2] crypto/ipsec_mb: " Brian Dooley
2023-07-06 16:14 ` Power, Ciara
2023-07-06 16:04 ` [PATCH v2 2/2] common/qat: change define header Brian Dooley
2023-07-06 16:12 ` Power, Ciara
2023-07-06 16:21 ` [PATCH v3 0/2] remove unused defines Brian Dooley
2023-07-06 16:21 ` [PATCH v3 1/2] crypto/ipsec_mb: " Brian Dooley
2023-07-07 11:38 ` Maxime Coquelin [this message]
2023-07-06 16:21 ` [PATCH v3 2/2] common/qat: change define header Brian Dooley
2023-07-06 18:31 ` [EXT] [PATCH v3 0/2] remove unused defines 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=7db1bcbd-2e7b-6b32-cade-23958448c4be@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=kai.ji@intel.com \
--cc=pablo.de.lara.guarch@intel.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).