From: Thomas Monjalon <thomas@monjalon.net>
To: Vladimir Kuramshin <v.kuramshin@samsung.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
tomasz.kantecki@intel.com
Subject: Re: [PATCH v4] examples/l2fwd-cat: fix build according to API changes
Date: Sat, 14 Oct 2017 00:28:07 +0200 [thread overview]
Message-ID: <2684122.DIe7DrKBq0@xps> (raw)
In-Reply-To: <20170919104736.GA20464@bricha3-MOBL3.ger.corp.intel.com>
19/09/2017 12:47, Bruce Richardson:
> On Tue, Sep 19, 2017 at 12:40:44PM +0300, Vladimir Kuramshin wrote:
> > Current version is compatible with PQOS version 1.3
> > but not compatible with higher versions. This change
> > makes l2fwd-cat example compatible with versions since 1.4
> >
> > Signed-off-by: Vladimir Kuramshin <v.kuramshin@samsung.com>
> > ---
> > Version 4 changes:
> > Fixed version number - 103 instead of 10300
> >
> > Version 3 changes:
> > Keep both API versions under #if .. #else .. #endif macro
> >
> > examples/l2fwd-cat/Makefile | 5 +--
> > examples/l2fwd-cat/cat.c | 85 +++++++++++++++++++++++++++++++++++++++------
> > 2 files changed, 76 insertions(+), 14 deletions(-)
> >
>
> Confirmed this builds fine with latest version of library from git.
>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied, thanks
prev parent reply other threads:[~2017-10-13 22:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170829095235eucas1p1c53a2ad6ba980aad25d51dfb6c6b8dd7@eucas1p1.samsung.com>
2017-08-29 9:51 ` [PATCH] examples/l2fwd-cat: fix build according to API changes Vladimir Kuramshin
2017-09-07 11:45 ` [PATCH v2] " Vladimir Kuramshin
2017-09-18 14:49 ` Bruce Richardson
2017-09-18 16:07 ` Vladimir Kuramshin
2017-09-18 16:18 ` Bruce Richardson
2017-09-19 8:17 ` [PATCH v3] " Vladimir Kuramshin
2017-09-19 8:56 ` Bruce Richardson
2017-09-19 9:23 ` Vladimir Kuramshin
2017-09-19 9:40 ` [PATCH v4] " Vladimir Kuramshin
2017-09-19 10:47 ` Bruce Richardson
2017-10-13 22:28 ` 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=2684122.DIe7DrKBq0@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=tomasz.kantecki@intel.com \
--cc=v.kuramshin@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.