From: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
To: stable@dpdk.org
Cc: bluca@debian.org, alialnu@nvidia.com
Subject: [dpdk-stable] [PATCH 19.11] net/mlx5: fix debug configuration build issue
Date: Wed, 16 Dec 2020 15:30:48 +0000 [thread overview]
Message-ID: <1608132648-15469-1-git-send-email-viacheslavo@nvidia.com> (raw)
If debugging options to generate assert are configured there was
build failure due to wrong variable naming pushed from backported
patch (see "Fixes" tag).
This fix is for 19.11 LTS only, issue origin is in 19.11 LTS only,
not in Upstream.
Fixes: ce4c764761d0 ("net/mlx5: fix port shared data reference count")
Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
---
drivers/net/mlx5/mlx5.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/mlx5/mlx5.c b/drivers/net/mlx5/mlx5.c
index 36e6937..4307005 100644
--- a/drivers/net/mlx5/mlx5.c
+++ b/drivers/net/mlx5/mlx5.c
@@ -1046,7 +1046,7 @@ struct mlx5_flow_id_pool *
{
struct mlx5_ibv_shared *sh = priv->sh;
- assert(sh && sh->dv_refcnt);
+ assert(sh && sh->refcnt);
if (sh->refcnt > 1)
return;
#ifdef HAVE_MLX5DV_DR
--
1.8.3.1
next reply other threads:[~2020-12-16 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 15:30 Viacheslav Ovsiienko [this message]
2020-12-17 9:26 ` Luca Boccassi
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=1608132648-15469-1-git-send-email-viacheslavo@nvidia.com \
--to=viacheslavo@nvidia.com \
--cc=alialnu@nvidia.com \
--cc=bluca@debian.org \
--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).