DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Gregory Etelson <getelson@nvidia.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Slava Ovsiienko <viacheslavo@nvidia.com>
Cc: "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
	Matan Azrad <matan@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: fix debug variable initialization
Date: Thu, 4 Nov 2021 14:00:17 +0000	[thread overview]
Message-ID: <DM4PR12MB5312EB6678D715FDD9DF27FECF8D9@DM4PR12MB5312.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20211104132853.31403-1-getelson@nvidia.com>

Hi,

> -----Original Message-----
> From: Gregory Etelson <getelson@nvidia.com>
> Sent: Thursday, November 4, 2021 3:29 PM
> To: dev@dpdk.org; Gregory Etelson <getelson@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>
> Cc: ferruh.yigit@intel.com; Raslan Darawsheh <rasland@nvidia.com>; Matan
> Azrad <matan@nvidia.com>
> Subject: [PATCH v2] net/mlx5: fix debug variable initialization
> 
> MLX5_ASSERT macro expansion depends on RTE_LIBRTE_MLX5_DEBUG and
> RTE_ENABLE_ASSERT.
> Existing implementation ignored the RTE_ENABLE_ASSERT dependency in
> the mlx5_flex_flow_translate_item() scope.
> As the result, the `priv` variable was not defined.
> 
> Fixes: 91f0e029ce5f ("net/mlx5: translate flex item pattern into matcher")
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>

Squashed into relevant commit in next-net-mlx,

Kindest regards,
Raslan Darawsheh

      reply	other threads:[~2021-11-04 14:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 12:23 [dpdk-dev] [PATCH] " Gregory Etelson
2021-11-04 12:31 ` Ferruh Yigit
2021-11-04 13:31   ` Gregory Etelson
2021-11-04 13:28 ` [dpdk-dev] [PATCH v2] " Gregory Etelson
2021-11-04 14:00   ` Raslan Darawsheh [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=DM4PR12MB5312EB6678D715FDD9DF27FECF8D9@DM4PR12MB5312.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=getelson@nvidia.com \
    --cc=matan@nvidia.com \
    --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).