From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: dev@dpdk.org
Cc: shreyansh.jain@nxp.com, stable@dpdk.org
Subject: [dpdk-dev] [PATCH 1/5] raw/dpaa2_qdma: fix spin lock release condition
Date: Wed, 24 Apr 2019 17:15:16 +0530 [thread overview]
Message-ID: <20190424114520.23655-1-hemant.agrawal@nxp.com> (raw)
Message-ID: <20190424114516.pOZwrt3ikJ_flUeeIcewKBSQ7pp_9AxAe0jw84beqes@z> (raw)
The code shall be unlock post the lock.
Fixes: c22fab9a6c34 ("raw/dpaa2_qdma: support configuration APIs")
Cc: stable@dpdk.org
Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
---
drivers/raw/dpaa2_qdma/dpaa2_qdma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/raw/dpaa2_qdma/dpaa2_qdma.c b/drivers/raw/dpaa2_qdma/dpaa2_qdma.c
index a41c1e385..102d423c6 100644
--- a/drivers/raw/dpaa2_qdma/dpaa2_qdma.c
+++ b/drivers/raw/dpaa2_qdma/dpaa2_qdma.c
@@ -984,7 +984,7 @@ rte_qdma_vq_destroy(uint16_t vq_id)
memset(qdma_vq, 0, sizeof(struct qdma_virt_queue));
- rte_spinlock_lock(&qdma_dev.lock);
+ rte_spinlock_unlock(&qdma_dev.lock);
return 0;
}
--
2.17.1
next reply other threads:[~2019-04-24 11:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 11:45 Hemant Agrawal [this message]
2019-04-24 11:45 ` Hemant Agrawal
2019-04-24 11:45 ` [dpdk-dev] [PATCH 2/5] raw/dpaa2_qdma: fix spin lock Hemant Agrawal
2019-04-24 11:45 ` Hemant Agrawal
2019-04-24 11:45 ` [dpdk-dev] [PATCH 3/5] net/dpaa2: fix the loopback spelling Hemant Agrawal
2019-04-24 11:45 ` Hemant Agrawal
2019-04-24 11:45 ` [dpdk-dev] [PATCH 4/5] doc: update the dpaaX platform guides Hemant Agrawal
2019-04-24 11:45 ` Hemant Agrawal
2019-05-02 15:56 ` Mcnamara, John
2019-05-02 15:56 ` Mcnamara, John
2019-04-24 11:45 ` [dpdk-dev] [PATCH 5/5] raw/dpaa2_cmdif: remove driver name assignment Hemant Agrawal
2019-04-24 11:45 ` Hemant Agrawal
2019-05-02 21:31 ` [dpdk-dev] [dpdk-stable] [PATCH 1/5] raw/dpaa2_qdma: fix spin lock release condition Thomas Monjalon
2019-05-02 21:31 ` Thomas Monjalon
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=20190424114520.23655-1-hemant.agrawal@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=shreyansh.jain@nxp.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).