DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xu, Rosen" <rosen.xu@intel.com>
To: David Marchand <david.marchand@redhat.com>,
	"Zhang, Tianfei" <tianfei.zhang@intel.com>
Cc: dev <dev@dpdk.org>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] raw/ifpga/base: dereference before null check
Date: Fri, 25 Oct 2019 01:05:02 +0000	[thread overview]
Message-ID: <0E78D399C70DA940A335608C6ED296D73AAE006A@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CAJFAV8yi2PPHa2-jOg0v8tU5baN1tn2h5qh8=WNr2NKQ0gBeNQ@mail.gmail.com>

Hi,

> -----Original Message-----
> From: David Marchand [mailto:david.marchand@redhat.com]
> Sent: Friday, October 25, 2019 3:22
> To: Xu, Rosen <rosen.xu@intel.com>; Zhang, Tianfei
> <tianfei.zhang@intel.com>
> Cc: dev <dev@dpdk.org>; dpdk stable <stable@dpdk.org>
> Subject: Re: [dpdk-dev] [PATCH] raw/ifpga/base: dereference before null
> check
> 
> On Tue, Sep 17, 2019 at 4:38 PM Tianfei zhang <tianfei.zhang@intel.com>
> wrote:
> >
> > Add pointer null check before dereference.
> >
> > Coverity issue: 344976
> > Fixes: 12f92a51 ("raw/ifpga/base: fix retimer link status")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Tianfei zhang <tianfei.zhang@intel.com>
> 
> This patch touches a "base driver" file, is this ok ?

It's just raw/ifpga internal base driver.

> 
> --
> David Marchand


  reply	other threads:[~2019-10-25  1:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-17 22:24 Tianfei zhang
2019-10-24 19:22 ` David Marchand
2019-10-25  1:05   ` Xu, Rosen [this message]
2019-10-25  2:40 ` Ye Xiaolong
2019-10-25 10:29   ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2019-10-25 11:47     ` David Marchand
2019-10-25 12:16       ` Thomas Monjalon
2019-10-28  5:47         ` Ye Xiaolong

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=0E78D399C70DA940A335608C6ED296D73AAE006A@SHSMSX104.ccr.corp.intel.com \
    --to=rosen.xu@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=tianfei.zhang@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).