From: Jeff Guo <jia.guo@intel.com>
To: wangyunjian <wangyunjian@huawei.com>, dev@dpdk.org
Cc: jerry.lilijun@huawei.com, xudingke@huawei.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 3/3] eal: return error code when failure
Date: Thu, 2 Jul 2020 17:18:47 +0800 [thread overview]
Message-ID: <058d3d03-ccd4-f8f1-c489-5b6525867516@intel.com> (raw)
In-Reply-To: <65433c2a9efdb47b1c9dba63d9bd1cb160e08097.1591186247.git.wangyunjian@huawei.com>
hi, yunjian
On 6/3/2020 8:55 PM, wangyunjian wrote:
> From: Yunjian Wang <wangyunjian@huawei.com>
>
> Fix return value, using -EAGAIN instead of 0 when the callback is busy
> and using -ENOENT instead of 0 when the callback is not found.
>
> Fixes: a753e53d517b ("eal: add device event monitor framework")
> Cc: stable@dpdk.org
>
> Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
> ---
> lib/librte_eal/common/eal_common_dev.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/lib/librte_eal/common/eal_common_dev.c b/lib/librte_eal/common/eal_common_dev.c
> index 6b465bc..5f5e333 100644
> --- a/lib/librte_eal/common/eal_common_dev.c
> +++ b/lib/librte_eal/common/eal_common_dev.c
> @@ -536,9 +536,14 @@ static int cmp_dev_name(const struct rte_device *dev, const void *_name)
> free(event_cb);
> ret++;
> } else {
> - continue;
> + ret = -EAGAIN;
> + break;
> }
> }
Suggest add a blank line here if there will be another version.
> + /* this callback is not be registered */
> + if (ret == 0)
> + ret = -ENOENT;
> +
> rte_spinlock_unlock(&dev_event_lock);
> return ret;
> }
Look good and thanks.
Acked-by: Jeff Guo <jia.guo@intel.com>
next prev parent reply other threads:[~2020-07-02 9:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 12:33 [dpdk-dev] [PATCH 0/3] fixes for device event wangyunjian
2020-06-03 12:54 ` wangyunjian
2020-06-03 12:54 ` [dpdk-dev] [PATCH 1/3] eal: fix memory leak when removing event_cb wangyunjian
2020-06-03 12:55 ` [dpdk-dev] [PATCH 2/3] eal: fix remove incorrect event_cb wangyunjian
2020-06-12 5:56 ` Jeff Guo
2020-06-30 11:29 ` wangyunjian
2020-06-30 11:56 ` [dpdk-dev] [PATCH v2] eal: fix memory leak when removing event_cb wangyunjian
2020-07-02 9:28 ` Jeff Guo
2020-07-02 10:53 ` wangyunjian
2020-07-02 11:46 ` [dpdk-dev] [PATCH v3 0/2] fixes for device event wangyunjian
2020-07-02 11:47 ` [dpdk-dev] [PATCH v3 1/2] eal: fix memory leak when removing event_cb wangyunjian
2020-07-03 6:04 ` Jeff Guo
2020-07-03 7:00 ` wangyunjian
2020-07-03 7:23 ` [dpdk-dev] [dpdk-stable] " David Marchand
2020-07-03 7:52 ` wangyunjian
2020-07-03 8:01 ` David Marchand
2020-07-02 11:47 ` [dpdk-dev] [PATCH v3 2/2] eal: return error code when failure wangyunjian
2020-06-03 12:55 ` [dpdk-dev] [PATCH 3/3] " wangyunjian
2020-07-02 9:18 ` Jeff Guo [this message]
2020-07-02 10:43 ` wangyunjian
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=058d3d03-ccd4-f8f1-c489-5b6525867516@intel.com \
--to=jia.guo@intel.com \
--cc=dev@dpdk.org \
--cc=jerry.lilijun@huawei.com \
--cc=stable@dpdk.org \
--cc=wangyunjian@huawei.com \
--cc=xudingke@huawei.com \
/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).