patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Gaetan Rivet <gaetan.rivet@6wind.com>, dev@dpdk.org
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	Nelio Laranjeiro <nelio.laranjeiro@6wind.com>,
	stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v2 1/2] net/mlx4: fix returned values upon failed probing
Date: Wed, 19 Apr 2017 16:58:50 +0100	[thread overview]
Message-ID: <536c9cc3-ec5b-fd1a-e5ca-ccb61ddde231@intel.com> (raw)
In-Reply-To: <07af53e20549d11c6a83973d2c413a9761d20bc3.1490710280.git.gaetan.rivet@6wind.com>

On 3/28/2017 3:13 PM, Gaetan Rivet wrote:
> Let error messages in place, but return unambiguous values upon
> probing errors.
> 
> Fixes: 66e1591687ac ("mlx4: avoid init errors when kernel modules are not loaded")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
> Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>

Series applied to dpdk-next-net/master, thanks.

(These were included into RC1, patches updated in patchwork, but it
seems missed notifying via e-mail, which is done now)

  reply	other threads:[~2017-04-19 15:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 14:17 [dpdk-stable] [PATCH " Gaetan Rivet
2017-03-27 14:17 ` [dpdk-stable] [PATCH 2/2] net/mlx5: " Gaetan Rivet
2017-03-28 10:15 ` [dpdk-stable] [PATCH 1/2] net/mlx4: " Ferruh Yigit
2017-03-28 14:14   ` Gaëtan Rivet
2017-03-28 14:13 ` [dpdk-stable] [PATCH v2 " Gaetan Rivet
2017-04-19 15:58   ` Ferruh Yigit [this message]
2017-03-28 14:13 ` [dpdk-stable] [PATCH v2 2/2] net/mlx5: " Gaetan Rivet

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=536c9cc3-ec5b-fd1a-e5ca-ccb61ddde231@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=gaetan.rivet@6wind.com \
    --cc=nelio.laranjeiro@6wind.com \
    --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).