From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Zapolski, MarcinX A" <marcinx.a.zapolski@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
"Zapolski, MarcinX A" <marcinx.a.zapolski@intel.com>
Subject: Re: [dpdk-dev] [PATCH] examples/ip_frag: fix stale content of eth info struct
Date: Mon, 22 Jul 2019 12:21:16 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB9772580168A58C9C@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <20190722114701.1001-1-marcinx.a.zapolski@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Marcin Zapolski
> Sent: Monday, July 22, 2019 12:47 PM
> To: dev@dpdk.org
> Cc: Richardson, Bruce <bruce.richardson@intel.com>; Zapolski, MarcinX A <marcinx.a.zapolski@intel.com>
> Subject: [dpdk-dev] [PATCH] examples/ip_frag: fix stale content of eth info struct
>
> The eth_dev_info was used with content that was obsolete. Added update
> of struct content prior to use.
>
> Fixes: 6b7780bfebe4 ("examples/ip_frag: fix use of ethdev internal device array")
>
> Signed-off-by: Marcin Zapolski <marcinx.a.zapolski@intel.com>
> ---
> examples/ip_fragmentation/main.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/examples/ip_fragmentation/main.c b/examples/ip_fragmentation/main.c
> index edf87a1a1..03be0c12e 100644
> --- a/examples/ip_fragmentation/main.c
> +++ b/examples/ip_fragmentation/main.c
> @@ -987,6 +987,7 @@ main(int argc, char **argv)
> printf("\n");
>
> /* init one TX queue per couple (lcore,port) */
> + rte_eth_dev_info_get(portid, &dev_info);
> queueid = 0;
> for (lcore_id = 0; lcore_id < RTE_MAX_LCORE; lcore_id++) {
> if (rte_lcore_is_enabled(lcore_id) == 0)
> --
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> 2.17.1
next prev parent reply other threads:[~2019-07-22 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 11:47 Marcin Zapolski
2019-07-22 12:21 ` Ananyev, Konstantin [this message]
2019-07-22 17:10 ` Thomas Monjalon
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=2601191342CEEE43887BDE71AB9772580168A58C9C@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=marcinx.a.zapolski@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).