dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>,
	Bing Zhao <bingz@mellanox.com>,
	Raslan Darawsheh <rasland@mellanox.com>
Cc: Ori Kam <orika@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix compiling without definition
Date: Mon, 11 Nov 2019 13:10:50 +0000	[thread overview]
Message-ID: <8d5d457f-732c-4635-b631-fd3406ce8f0b@intel.com> (raw)
In-Reply-To: <AM4PR05MB3265CD6EAE10EF8F7F177DECD2740@AM4PR05MB3265.eurprd05.prod.outlook.com>

On 11/11/2019 7:00 AM, Slava Ovsiienko wrote:
>> -----Original Message-----
>> From: Bing Zhao <bingz@mellanox.com>
>> Sent: Sunday, November 10, 2019 18:37
>> To: Slava Ovsiienko <viacheslavo@mellanox.com>; Raslan Darawsheh
>> <rasland@mellanox.com>
>> Cc: Ori Kam <orika@mellanox.com>; dev@dpdk.org
>> Subject: [PATCH] net/mlx5: fix compiling without definition
>>
>> When compiling the driver without macro for direct rules, the flow table
>> reference count should also be in the flow table resource structure.
>>
>> Fixes: c7455199284a ("net/mlx5: reorganize flow tables with hash list")
>>
>> Signed-off-by: Bing Zhao <bingz@mellanox.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> 

Squashed into relevant commit in next-net, thanks.

Please confirm the change in latest next-net.

      reply	other threads:[~2019-11-11 13:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10 16:37 [dpdk-dev] [PATCH] net/mlx5: fix compiling without definition Bing Zhao
2019-11-11  7:00 ` Slava Ovsiienko
2019-11-11 13:10   ` 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=8d5d457f-732c-4635-b631-fd3406ce8f0b@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bingz@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=orika@mellanox.com \
    --cc=rasland@mellanox.com \
    --cc=viacheslavo@mellanox.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).