From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Michal Jastrzebski <michalx.k.jastrzebski@intel.com>,
Michal Kobylinski <michalx.kobylinski@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] app: fix for lpm in ip_pipeline
Date: Fri, 18 Mar 2016 11:51:51 +0100 [thread overview]
Message-ID: <9202117.3kppz4Lca4@xps13> (raw)
In-Reply-To: <1458204445-7480-1-git-send-email-michalx.k.jastrzebski@intel.com>
2016-03-17 09:47, Michal Jastrzebski:
> From: Michal Kobylinski <michalx.kobylinski@intel.com>
>
> Updated ip_pipeline app is using new changes from LPM library
> (Increased number of next hops and added new config structure
> for LPM IPv4).
>
> Fixes: 7164439d017d ("lpm: add a new config structure for IPv4")
Fixes: f1f7261838b3 ("lpm: add a new config structure for IPv4")
> Signed-off-by: Michal Kobylinski <michalx.kobylinski@intel.com>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Applied, thanks
prev parent reply other threads:[~2016-03-18 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 8:47 Michal Jastrzebski
2016-03-18 10:51 ` 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=9202117.3kppz4Lca4@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=michalx.k.jastrzebski@intel.com \
--cc=michalx.kobylinski@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).