DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: stable@dpdk.org, dev@dpdk.org, shreyansh.jain@nxp.com
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH 1/5] raw/dpaa2_qdma: fix spin lock release condition
Date: Thu, 02 May 2019 23:31:53 +0200	[thread overview]
Message-ID: <3936007.3bICKcIKC4@xps> (raw)
In-Reply-To: <20190424114520.23655-1-hemant.agrawal@nxp.com>

24/04/2019 13:45, Hemant Agrawal:
> 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>

Series applied, thanks

  parent reply	other threads:[~2019-05-02 21:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 11:45 [dpdk-dev] " Hemant Agrawal
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 ` Thomas Monjalon [this message]
2019-05-02 21:31   ` [dpdk-dev] [dpdk-stable] [PATCH 1/5] raw/dpaa2_qdma: fix spin lock release condition 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=3936007.3bICKcIKC4@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --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).