From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Gaetan Rivet <gaetan.rivet@6wind.com>, dev@dpdk.org
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 1/2] net/mlx4: fix returned values upon failed probing
Date: Tue, 28 Mar 2017 11:15:42 +0100 [thread overview]
Message-ID: <03745e21-2e54-616b-8d46-321136d9fcbb@intel.com> (raw)
In-Reply-To: <2f6db539fb06934a9433fea1e3ea64d5171db962.1490624067.git.gaetan.rivet@6wind.com>
On 3/27/2017 3:17 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>
Hi Gaetan,
I am getting merge conflict in this patch, can you please rebase it on
top of latest next-net?
Thanks,
ferruh
next prev parent reply other threads:[~2017-03-28 10:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 14:17 Gaetan Rivet
2017-03-27 14:17 ` [dpdk-stable] [PATCH 2/2] net/mlx5: " Gaetan Rivet
2017-03-28 10:15 ` Ferruh Yigit [this message]
2017-03-28 14:14 ` [dpdk-stable] [PATCH 1/2] net/mlx4: " Gaëtan Rivet
2017-03-28 14:13 ` [dpdk-stable] [PATCH v2 " Gaetan Rivet
2017-04-19 15:58 ` Ferruh Yigit
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=03745e21-2e54-616b-8d46-321136d9fcbb@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@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).