From: Akhil Goyal <gakhil@marvell.com>
To: Ganapati Kundapura <ganapati.kundapura@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"abhinandan.gujjar@intel.com" <abhinandan.gujjar@intel.com>,
"john.mcnamara@intel.com" <john.mcnamara@intel.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>
Cc: "mb@smartsharesystems.com" <mb@smartsharesystems.com>,
"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
"fanzhang.oss@gmail.com" <fanzhang.oss@gmail.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"bala.senthil@intel.com" <bala.senthil@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [EXTERNAL] [PATCH v4 1/2] cryptodev: fix crypto callbacks on unsetting callbacks macro
Date: Tue, 2 Jul 2024 15:24:36 +0000 [thread overview]
Message-ID: <CO6PR18MB448472EDD0408B39BC0B31DCD8DC2@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20240627100626.2430162-1-ganapati.kundapura@intel.com>
> Crypto callbacks APIs are available in header files but when
> the macro RTE_CRYPTO_CALLBACKS unset, test application need to
> put #ifdef in its code.
>
> The test application should be able to build and run, regardless
> DPDK library is built with RTE_CRYPTO_CALLBACKS defined or not.
>
> Added ENOTSUP from the beginning of the APIs implementation
> if RTE_CRYPTO_CALLBACKS macro is unset/undefined.
>
> Fixes: 1c3ffb95595e ("cryptodev: add enqueue and dequeue callbacks")
> Fixes: 5523a75af539 ("test/crypto: add case for enqueue/dequeue callbacks")
Cc: stable@dpdk.org
>
> Signed-off-by: Ganapati Kundapura <ganapati.kundapura@intel.com>
Acked-by: Akhil Goyal <gakhil@marvell.com>
Applied to dpdk-next-crypto
parent reply other threads:[~2024-07-02 15:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240627100626.2430162-1-ganapati.kundapura@intel.com>]
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=CO6PR18MB448472EDD0408B39BC0B31DCD8DC2@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=abhinandan.gujjar@intel.com \
--cc=bala.senthil@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=ferruh.yigit@amd.com \
--cc=ganapati.kundapura@intel.com \
--cc=john.mcnamara@intel.com \
--cc=mb@smartsharesystems.com \
--cc=stable@dpdk.org \
--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).