From: "Ji, Kai" <kai.ji@intel.com>
To: "pallard, didier" <didier.pallard@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"Mrzyglod, Daniel T" <daniel.t.mrzyglod@intel.com>,
Tomasz Kulasek <tomaszx.kulasek@intel.com>,
"Kobylinski, Michal" <michal.kobylinski@intel.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Mrozowicz, SlawomirX" <slawomirx.mrozowicz@intel.com>
Subject: Re: [PATCH] crypto/openssl: do not build useless workaround
Date: Tue, 20 Jun 2023 09:29:36 +0000 [thread overview]
Message-ID: <SN6PR11MB34089A1445A43A56160668D1815CA@SN6PR11MB3408.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230418145619.2648068-1-didier.pallard@6wind.com>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
Acked-by: Kai Ji <kai.ji@intel.com<mailto:kai.ji@intel.com>>
________________________________
From: Didier Pallard <didier.pallard@6wind.com>
Sent: 18 April 2023 15:56
To: dev@dpdk.org <dev@dpdk.org>
Cc: stable@dpdk.org <stable@dpdk.org>; Ji, Kai <kai.ji@intel.com>; Mrzyglod, Daniel T <daniel.t.mrzyglod@intel.com>; Tomasz Kulasek <tomaszx.kulasek@intel.com>; Kobylinski, Michal <michal.kobylinski@intel.com>; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Mrozowicz, SlawomirX <slawomirx.mrozowicz@intel.com>
Subject: [PATCH] crypto/openssl: do not build useless workaround
This workaround was needed before version 1.0.1f. Do not build it for
versions >= 1.1.
Fixes: d61f70b4c918 ("crypto/libcrypto: add driver for OpenSSL library")
Signed-off-by: Didier Pallard <didier.pallard@6wind.com>
Cc: stable@dpdk.org
---
drivers/crypto/openssl/rte_openssl_pmd.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
--
2.30.2
[-- Attachment #2: Type: text/html, Size: 2492 bytes --]
next prev parent reply other threads:[~2023-06-20 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 14:56 Didier Pallard
2023-06-20 9:29 ` Ji, Kai [this message]
2023-06-20 11:00 ` Akhil Goyal
2023-06-25 19:22 ` Thomas Monjalon
2023-06-26 9:13 ` Didier Pallard
2023-06-26 10:04 ` Thomas Monjalon
2023-06-26 10:39 ` Didier Pallard
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=SN6PR11MB34089A1445A43A56160668D1815CA@SN6PR11MB3408.namprd11.prod.outlook.com \
--to=kai.ji@intel.com \
--cc=daniel.t.mrzyglod@intel.com \
--cc=dev@dpdk.org \
--cc=didier.pallard@6wind.com \
--cc=michal.kobylinski@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=slawomirx.mrozowicz@intel.com \
--cc=stable@dpdk.org \
--cc=tomaszx.kulasek@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).