DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Wei Dai <wei.dai@intel.com>
Cc: dev@dpdk.org, Laurent Hardy <laurent.hardy@6wind.com>,
	"Roger B. Melton" <rmelton@cisco.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	wenzhuo.lu@intel.com, konstantin.ananyev@intel.com
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] net/ixgbe: fix calling null function of VF
Date: Wed, 10 May 2017 17:18:05 +0200	[thread overview]
Message-ID: <5042107.JggcIGmKYW@xps> (raw)
In-Reply-To: <59130895.90503@6wind.com>

10/05/2017 14:33, Laurent Hardy:
> Hi Ferruh, Wei, Roger,
> PSB
> I also redo test plan provided through 
> http://dpdk.org/dev/patchwork/patch/20502/
> 
> Thanks & regards,
> Laurent
> 
> On 05/10/2017 02:20 PM, Roger B. Melton wrote:
> >
> >
> > On 5/10/17 5:50 AM, Ferruh Yigit wrote:
> >> On 5/10/2017 8:00 AM, Wei Dai wrote:
> >>> hw->mac.ops.get_media-type() of ixgbe VF is NULL and should not
> >>> be called directly. It had better be replaced by calling
> >>> ixgbe_get_media_type( ) to avoid crash.
> >>>
> >>> Fixes: c12d22f65b13 ("net/ixgbe: ensure link status is updated")
> >>> Cc: stable@dpdk.org
> >>>
> >>> Signed-off-by: Wei Dai <wei.dai@intel.com>
> Acked-by: Laurent Hardy <laurent.hardy@6wind.com>

Removing stable@dpdk.org as the bug was introduced in 17.05-rc3.

Applied, thanks

  reply	other threads:[~2017-05-10 15:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10  7:00 [dpdk-dev] " Wei Dai
2017-05-10  9:34 ` Gregory Etelson
2017-05-10  9:49   ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2017-05-10  9:50 ` Ferruh Yigit
2017-05-10 12:20   ` Roger B. Melton
2017-05-10 12:33     ` Laurent Hardy
2017-05-10 15:18       ` Thomas Monjalon [this message]
2017-05-10 19:08 ` Roger B Melton

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=5042107.JggcIGmKYW@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=laurent.hardy@6wind.com \
    --cc=rmelton@cisco.com \
    --cc=wei.dai@intel.com \
    --cc=wenzhuo.lu@intel.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).