From: Luca Boccassi <bluca@debian.org>
To: Viacheslav Ovsiienko <viacheslavo@nvidia.com>, stable@dpdk.org
Cc: alialnu@nvidia.com
Subject: Re: [dpdk-stable] [PATCH 19.11] net/mlx5: fix debug configuration build issue
Date: Thu, 17 Dec 2020 09:26:22 +0000 [thread overview]
Message-ID: <00e248feed60027fb12f345e672b533e8601597f.camel@debian.org> (raw)
In-Reply-To: <1608132648-15469-1-git-send-email-viacheslavo@nvidia.com>
On Wed, 2020-12-16 at 15:30 +0000, Viacheslav Ovsiienko wrote:
> 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(-)
Thank you, applied. Must have made a mistake during a rebase, my bad.
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2020-12-17 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 15:30 Viacheslav Ovsiienko
2020-12-17 9:26 ` Luca Boccassi [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=00e248feed60027fb12f345e672b533e8601597f.camel@debian.org \
--to=bluca@debian.org \
--cc=alialnu@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@nvidia.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).