From: Akhil Goyal <akhil.goyal@nxp.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"ravi1.kumar@amd.com" <ravi1.kumar@amd.com>
Subject: Re: [dpdk-dev] [PATCH] test/crypto: fix duplicate device id uses by CCP device
Date: Wed, 6 Mar 2019 16:52:15 +0000 [thread overview]
Message-ID: <836609bc-2708-991e-f76e-f0f18932e508@nxp.com> (raw)
In-Reply-To: <20190222100518.7125-1-hemant.agrawal@nxp.com>
On 2/22/2019 3:36 PM, Hemant Agrawal wrote:
> These duplicate device id is causing incorrect mapping
> for DPAA_SEC for test case execultion on the basis of
> capabilities.
>
> Fixes: e155ca055e84 ("test/crypto: add tests for AMD CCP")
> Cc: stable@dpdk.org
> Cc: ravi1.kumar@amd.com
>
> Reported-by: Anoob Joseph <anoobj@marvell.com>
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> ---
> test/test/test_cryptodev_blockcipher.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/test/test/test_cryptodev_blockcipher.h b/test/test/test_cryptodev_blockcipher.h
> index 5c22d5da6..d3a7edd99 100644
> --- a/test/test/test_cryptodev_blockcipher.h
> +++ b/test/test/test_cryptodev_blockcipher.h
> @@ -27,10 +27,10 @@
> #define BLOCKCIPHER_TEST_TARGET_PMD_DPAA2_SEC 0x0020 /* DPAA2_SEC flag */
> #define BLOCKCIPHER_TEST_TARGET_PMD_DPAA_SEC 0x0040 /* DPAA_SEC flag */
> #define BLOCKCIPHER_TEST_TARGET_PMD_MVSAM 0x0080 /* Marvell flag */
> -#define BLOCKCIPHER_TEST_TARGET_PMD_CCP 0x0040 /* CCP flag */
> #define BLOCKCIPHER_TEST_TARGET_PMD_VIRTIO 0x0200 /* VIRTIO flag */
> #define BLOCKCIPHER_TEST_TARGET_PMD_OCTEONTX 0x0100 /* OCTEON TX flag */
> #define BLOCKCIPHER_TEST_TARGET_PMD_CAAM_JR 0x0400 /* CAAM_JR flag */
> +#define BLOCKCIPHER_TEST_TARGET_PMD_CCP 0x0800 /* CCP flag */
>
> #define BLOCKCIPHER_TEST_OP_CIPHER (BLOCKCIPHER_TEST_OP_ENCRYPT | \
> BLOCKCIPHER_TEST_OP_DECRYPT)
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
rebased and Applied to dpdk-next-crypto
Thanks
prev parent reply other threads:[~2019-03-06 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 10:06 Hemant Agrawal
2019-03-06 16:52 ` 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=836609bc-2708-991e-f76e-f0f18932e508@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=ravi1.kumar@amd.com \
--cc=stable@dpdk.org \
/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).