From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ricardo Roldan <rroldan@bequant.com>, dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>,
Andrew Rybchenko <arybchenko@solarflare.com>
Subject: Re: [dpdk-dev] [PATCH] ethdev: rte_eth_dev_callback_unregister() fails with cb_arg == -1
Date: Mon, 13 Jan 2020 16:45:32 +0000 [thread overview]
Message-ID: <070042ce-e1ef-117e-9d4a-d8cb292fcf8f@intel.com> (raw)
In-Reply-To: <20200107155136.70237-1-rroldan@bequant.com>
On 1/7/2020 3:51 PM, Ricardo Roldan wrote:
> The function was checking -1 against the callback data instead of
> the given cb_arg parameter.
>
> Signed-off-by: Ricardo Roldan <rroldan@bequant.com>
Updated title as:
ethdev: fix callback unregister with wildcard argument list
Also adding following metadata to the commit log:
Fixes: af75078fece3 ("first public release")
Cc: stable@dpdk.org
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
(This bug seems as old as DPDK itself J, thanks for fixing it.)
prev parent reply other threads:[~2020-01-13 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 15:51 [dpdk-dev] [PATCH] ethdev: rte_eth_dev_callback_unregister() fails with cb_arg == -1 Ricardo Roldan
2020-01-13 16:45 ` Ferruh Yigit [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=070042ce-e1ef-117e-9d4a-d8cb292fcf8f@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=rroldan@bequant.com \
--cc=thomas@monjalon.net \
/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).