DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	Matan Azrad <matan@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx4: revert workaround for broken Verbs
Date: Wed, 6 Dec 2017 06:39:10 +0000	[thread overview]
Message-ID: <VI1PR05MB3149E4A7C181ECD325E1B829C3320@VI1PR05MB3149.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20171204165239.GJ4062@6wind.com>

Monday, December 4, 2017 6:53 PM, Adrien Mazarguil:
> On Wed, Nov 29, 2017 at 09:21:26AM +0000, Matan Azrad wrote:
> > This workaround was needed to properly handle device removal with old
> > Mellanox OFED releases that are not supported by this PMD anymore.
> >
> > Starting from rdma-core v16 this removal issue shouldn't happen when
> > setting MLX4_DEVICE_FATAL_CLEANUP environment variable to 1.
> >
> > Set the aforementioned variable to 1.
> >
> > Reverts: 5f4677c ("net/mlx4: workaround verbs error after plug-out")
> >
> > Signed-off-by: Matan Azrad <matan@mellanox.com>
> 
> You should expand the commit ID a bit:
> 
> Reverts: 5f4677c6ad5e ("net/mlx4: workaround verbs error after plug-out")
> 
> Other than that,
> 
> Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>

Applied the next-net-mlx with the above commit log fix, thanks.

> 
> Thanks.
> 
> --
> Adrien Mazarguil
> 6WIND

      reply	other threads:[~2017-12-06  6:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29  9:21 Matan Azrad
2017-12-04 16:52 ` Adrien Mazarguil
2017-12-06  6:39   ` Shahaf Shuler [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=VI1PR05MB3149E4A7C181ECD325E1B829C3320@VI1PR05MB3149.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=matan@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).