From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"igor.romanov@oktetlabs.ru" <igor.romanov@oktetlabs.ru>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] examples/ipsec-segw: add SPDX license tag
Date: Fri, 8 Nov 2019 18:28:16 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB97725801A8C839EA@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <20191108170614.8895-1-stephen@networkplumber.org>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
> examples/ipsec-secgw/test/bypass_defs.sh | 1 +
> examples/ipsec-secgw/test/common_defs.sh | 1 +
> examples/ipsec-secgw/test/common_defs_secgw.sh | 1 +
> examples/ipsec-secgw/test/data_rxtx.sh | 1 +
> examples/ipsec-secgw/test/linux_test4.sh | 1 +
> examples/ipsec-secgw/test/linux_test6.sh | 1 +
> examples/ipsec-secgw/test/pkttest.py | 1 +
> examples/ipsec-secgw/test/pkttest.sh | 1 +
> examples/ipsec-secgw/test/run_test.sh | 1 +
> examples/ipsec-secgw/test/trs_3descbc_sha1_common_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_3descbc_sha1_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_3descbc_sha1_esn_atom_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_3descbc_sha1_esn_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_3descbc_sha1_old_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_aescbc_sha1_common_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_aescbc_sha1_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_aescbc_sha1_esn_atom_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_aescbc_sha1_esn_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_aescbc_sha1_old_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_aesctr_sha1_common_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_aesctr_sha1_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_aesctr_sha1_esn_atom_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_aesctr_sha1_esn_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_aesctr_sha1_old_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_aesgcm_common_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_aesgcm_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_aesgcm_esn_atom_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_aesgcm_esn_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_aesgcm_inline_crypto_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_aesgcm_inline_crypto_old_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_aesgcm_old_defs.sh | 1 +
> examples/ipsec-secgw/test/trs_ipv6opts.py | 1 +
> examples/ipsec-secgw/test/tun_3descbc_sha1_common_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_3descbc_sha1_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_3descbc_sha1_esn_atom_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_3descbc_sha1_esn_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_3descbc_sha1_old_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_aescbc_sha1_common_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_aescbc_sha1_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_aescbc_sha1_esn_atom_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_aescbc_sha1_esn_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_aescbc_sha1_old_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_aesctr_sha1_common_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_aesctr_sha1_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_aesctr_sha1_esn_atom_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_aesctr_sha1_esn_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_aesctr_sha1_old_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_aesgcm_common_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_aesgcm_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_aesgcm_esn_atom_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_aesgcm_esn_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_aesgcm_inline_crypto_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_aesgcm_inline_crypto_old_defs.sh | 1 +
> examples/ipsec-secgw/test/tun_aesgcm_old_defs.sh | 1 +
> 54 files changed, 54 insertions(+)
>
> --
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> 2.20.1
next prev parent reply other threads:[~2019-11-08 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 17:06 Stephen Hemminger
2019-11-08 18:28 ` Ananyev, Konstantin [this message]
2019-11-18 7:56 ` Akhil Goyal
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=2601191342CEEE43887BDE71AB97725801A8C839EA@IRSMSX104.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=igor.romanov@oktetlabs.ru \
--cc=stephen@networkplumber.org \
/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).