From: Thomas Monjalon <thomas@monjalon.net>
To: "Zapolski, MarcinX A" <marcinx.a.zapolski@intel.com>
Cc: dev@dpdk.org, "Ananyev,
Konstantin" <konstantin.ananyev@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] examples/ip_frag: fix stale content of eth info struct
Date: Mon, 22 Jul 2019 19:10:59 +0200 [thread overview]
Message-ID: <3467141.CDSSb380cO@xps> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB9772580168A58C9C@irsmsx105.ger.corp.intel.com>
22/07/2019 14:21, Ananyev, Konstantin:
> From: Marcin Zapolski
> > 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")
Cc: stable@dpdk.org
> >
> > Signed-off-by: Marcin Zapolski <marcinx.a.zapolski@intel.com>
>
> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Looks like previous patch was not tested :)
Applied, thanks
prev parent reply other threads:[~2019-07-22 17:11 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
2019-07-22 17:10 ` Thomas Monjalon [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=3467141.CDSSb380cO@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=marcinx.a.zapolski@intel.com \
--cc=stable@dpdk.org \
/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).