From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Smoczynski, MarcinX" <marcinx.smoczynski@intel.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.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: Wed, 2 Oct 2019 08:53:29 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB977258019196FB7E@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <20191002085016.10520-1-marcinx.smoczynski@intel.com>
> -----Original Message-----
> From: Smoczynski, MarcinX
> Sent: Wednesday, October 2, 2019 9:50 AM
> To: akhil.goyal@nxp.com; Ananyev, Konstantin <konstantin.ananyev@intel.com>; Iremonger, Bernard <bernard.iremonger@intel.com>
> Cc: dev@dpdk.org; Smoczynski, MarcinX <marcinx.smoczynski@intel.com>
> Subject: [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.
> Accept future versions of Scapy too.
>
> Signed-off-by: Marcin Smoczynski <marcinx.smoczynski@intel.com>
> ---
> examples/ipsec-secgw/test/pkttest.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/examples/ipsec-secgw/test/pkttest.py b/examples/ipsec-secgw/test/pkttest.py
> index bcad2156b..5250727f4 100755
> --- a/examples/ipsec-secgw/test/pkttest.py
> +++ b/examples/ipsec-secgw/test/pkttest.py
> @@ -21,7 +21,7 @@
>
>
> PKTTEST_REQ = [
> - "scapy==2.4.3rc1",
> + "scapy>=2.4.3",
> ]
>
>
> --
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> 2.17.1
next prev parent reply other threads:[~2019-10-02 8:53 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 [this message]
2019-10-03 8:29 ` Akhil Goyal
2019-10-03 8:55 ` Smoczynski, MarcinX
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=2601191342CEEE43887BDE71AB977258019196FB7E@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=marcinx.smoczynski@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).