From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
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:02:50 +0100 [thread overview]
Message-ID: <83ac240f-6a3f-2785-0ed2-2f31959c0475@intel.com> (raw)
In-Reply-To: <2455076.tMWrylkWj2@xps>
On 5/9/2018 11:50 PM, Thomas Monjalon wrote:
> 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>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-05-09 23:02 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
2018-05-09 23:02 ` Ferruh Yigit [this message]
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=83ac240f-6a3f-2785-0ed2-2f31959c0475@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=remy.horton@intel.com \
--cc=thomas@monjalon.net \
/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).