From: "Smoczynski, MarcinX" <marcinx.smoczynski@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Iremonger, Bernard" <bernard.iremonger@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] examples/ipsec-secgw: update pkttest requirements
Date: Thu, 3 Oct 2019 08:55:10 +0000 [thread overview]
Message-ID: <2F25558C1648FA498380EAC12A861262172E692E@hasmsx107.ger.corp.intel.com> (raw)
In-Reply-To: <VE1PR04MB66390040EA57A7DF39468755E69F0@VE1PR04MB6639.eurprd04.prod.outlook.com>
I've used 2.4.3rc1 in the first place because 2.4.2 which was the latest
version at that time had a bug which made it unable to install.
2.4.3rc1 worked fine.
2.4.3 has been released recently so we are moving from pre-release RC
to stable version. Thanks to ">=" in the requirement we won't need
to update it in the future.
> -----Original Message-----
> From: Akhil Goyal [mailto:akhil.goyal@nxp.com]
> Sent: Thursday, October 3, 2019 10:30 AM
> To: Ananyev, Konstantin <konstantin.ananyev@intel.com>; Smoczynski,
> MarcinX <marcinx.smoczynski@intel.com>; Iremonger, Bernard
> <bernard.iremonger@intel.com>
> Cc: dev@dpdk.org
> Subject: RE: [PATCH] examples/ipsec-secgw: update pkttest requirements
>
> > >
> > > Update Scapy version requirement from 2.4.3rc1 to 2.4.3, which has
> > > been used because 2.4.2 had a bug which made this version unable to
> install.
>
> Is this 2.4.2 or 2.4.3??
>
> > > Accept future versions of Scapy too.
> > >
> > > Signed-off-by: Marcin Smoczynski <marcinx.smoczynski@intel.com>
> >
> > Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> >
prev parent reply other threads:[~2019-10-03 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 8:50 Marcin Smoczynski
2019-10-02 8:53 ` Ananyev, Konstantin
2019-10-03 8:29 ` Akhil Goyal
2019-10-03 8:55 ` Smoczynski, MarcinX [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=2F25558C1648FA498380EAC12A861262172E692E@hasmsx107.ger.corp.intel.com \
--to=marcinx.smoczynski@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@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).