From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH] examples/l3fwd: use correct IP reserved address range
Date: Tue, 5 Nov 2019 08:32:47 -0800 [thread overview]
Message-ID: <20191105083247.386fb34e@hermes.lan> (raw)
In-Reply-To: <75e12b10-ebe0-e17d-799d-5d73956b85f2@intel.com>
On Tue, 5 Nov 2019 16:12:31 +0000
Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> On 11/5/2019 4:09 PM, Stephen Hemminger wrote:
> > The original patch used incorrect subnet range for testing.
> >
> > Fixes: 37afe381bde4 ("examples/l3fwd: use reserved IP addresses")
> > Reported-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> I guess this is:
> Reported-by: Hemant Agrawal <hemant.agrawal@nxp.com>
Go ahead add both!
next prev parent reply other threads:[~2019-11-05 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 16:09 Stephen Hemminger
2019-11-05 16:12 ` Ferruh Yigit
2019-11-05 16:32 ` Stephen Hemminger [this message]
2019-11-06 5:36 ` Hemant Agrawal
2019-11-07 20:52 ` David Marchand
2019-11-08 3:24 ` Stephen Hemminger
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=20191105083247.386fb34e@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.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).