DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, remy.horton@intel.com
Subject: Re: [dpdk-dev] [PATCH] ethdev: fix corrupted device info in configure
Date: Thu, 10 May 2018 00:50:37 +0200	[thread overview]
Message-ID: <2455076.tMWrylkWj2@xps> (raw)
In-Reply-To: <20180509221649.129690-1-ferruh.yigit@intel.com>

10/05/2018 00:16, Ferruh Yigit:
> Calling dev_infos_get() devops directly in rte_eth_dev_configure cause
> random values in uninitialized fields because devops doesn't reset the
> dev_info structure.
> 
> Call rte_eth_dev_info_get() API instead which memset the struct.
> 
> Also remove duplicated dev_infos_get existence check.
> 
> Fixes: 3be82f5cc5e3 ("ethdev: support PMD-tuned Tx/Rx parameters")
> Cc: remy.horton@intel.com
> 
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>

Acked-by: Thomas Monjalon <thomas@monjalon.net>

  reply	other threads:[~2018-05-09 22:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09 22:16 Ferruh Yigit
2018-05-09 22:50 ` Thomas Monjalon [this message]
2018-05-09 23:02   ` 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:
  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=2455076.tMWrylkWj2@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=remy.horton@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).