From: Akhil Goyal <akhil.goyal@nxp.com>
To: <dev@dpdk.org>, <stable@dpdk.org>
Cc: <hemant.agrawal@nxp.com>, <pablo.de.lara.guarch@intel.com>,
<yliu@fridaylinux.org>, Akhil Goyal <akhil.goyal@nxp.com>
Subject: [dpdk-dev] [PATCH v2] crypto/dpaa2_sec: fix the return of supported API
Date: Tue, 18 Jul 2017 13:03:56 +0530 [thread overview]
Message-ID: <20170718073356.14288-1-akhil.goyal@nxp.com> (raw)
call to dpaa2_sec_dev_configure() is made mandatory,
but dpaa2_sec_pmd returns a ENOTSUP which results in
device not getting configured.
dpaa2_sec PMD does not need any further configuration
to be done in dpaa2_sec_dev_configure, hence returning 0
Fixes: e5cbdfc53765 ("crypto/dpaa2_sec: add basic operations")
Cc: stable@dpdk.org
Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com>
---
This patch is for stable 17.05 tree only.
This fix is already present in dpdk mainline
drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
index 4e01fe8..08fd085 100644
--- a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
+++ b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
@@ -1263,7 +1263,7 @@ dpaa2_sec_dev_configure(struct rte_cryptodev *dev __rte_unused,
{
PMD_INIT_FUNC_TRACE();
- return -ENOTSUP;
+ return 0;
}
static int
--
2.9.3
next reply other threads:[~2017-07-18 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 7:33 Akhil Goyal [this message]
2017-07-18 10:26 ` De Lara Guarch, Pablo
2017-07-18 14:39 ` Yuanhan Liu
2017-07-18 16:21 ` De Lara Guarch, Pablo
2017-07-18 17:32 ` Hemant Agrawal
2017-07-19 12:12 ` Yuanhan Liu
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=20170718073356.14288-1-akhil.goyal@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=stable@dpdk.org \
--cc=yliu@fridaylinux.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).