From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Sankar Chokkalingam <sankarx.chokkalingam@intel.com>
Cc: dev@dpdk.org, cristian.dumitrescu@intel.com
Subject: Re: [dpdk-dev] [PATCH] examples/ip_pipeline: fix wrong values in flow.cfg
Date: Thu, 28 Jul 2016 16:58:29 +0200 [thread overview]
Message-ID: <4666509.97gCXPrhXB@xps13> (raw)
In-Reply-To: <1469612130-19855-1-git-send-email-sankarx.chokkalingam@intel.com>
2016-07-27 02:35, Sankar Chokkalingam:
> This configuration is example configuration for flow classification.
> This fix changes the offset and mask value to compute the hash correctly.
> This fix does not involve code change and do not impact compilation,
> build and performance.
>
> Fixes: 93771a569daa ("examples/ip_pipeline: rework flow classification CLI")
>
> Signed-off-by: Sankar Chokkalingam <sankarx.chokkalingam@intel.com>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Applied, thanks
prev parent reply other threads:[~2016-07-28 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 9:35 Sankar Chokkalingam
2016-07-28 14:58 ` 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=4666509.97gCXPrhXB@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=sankarx.chokkalingam@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).