DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: wangyunjian <wangyunjian@huawei.com>, dev@dpdk.org
Cc: thomas@monjalon.net, andrew.rybchenko@oktetlabs.ru,
	jerry.lilijun@huawei.com, xudingke@huawei.com
Subject: Re: [dpdk-dev] [PATCH v2] ethdev: fix check of rx configure
Date: Wed, 4 Nov 2020 11:11:08 +0000	[thread overview]
Message-ID: <34c087e8-1c0c-afe9-9dc3-2ec4106302cf@intel.com> (raw)
In-Reply-To: <1604453076-34392-1-git-send-email-wangyunjian@huawei.com>

On 11/4/2020 1:24 AM, wangyunjian wrote:
> From: Yunjian Wang <wangyunjian@huawei.com>
> Coverity flags that 'rx_conf' variable is used before
> it's checked for NULL. This patch fixes this issue.
> Coverity issue: 363570
> Fixes: 4ff702b5dfa9 ("ethdev: introduce Rx buffer split")
> Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

  reply	other threads:[~2020-11-04 11:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 13:31 [dpdk-dev] [PATCH] " wangyunjian
2020-11-03 13:58 ` Ferruh Yigit
2020-11-04  1:15   ` wangyunjian
2020-11-04  1:24 ` [dpdk-dev] [PATCH v2] " wangyunjian
2020-11-04 11:11   ` Ferruh Yigit [this message]
2020-11-04 11:22     ` Ferruh Yigit

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=34c087e8-1c0c-afe9-9dc3-2ec4106302cf@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=jerry.lilijun@huawei.com \
    --cc=thomas@monjalon.net \
    --cc=wangyunjian@huawei.com \
    --cc=xudingke@huawei.com \


* 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).