DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Volodymyr Fialko <vfialko@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Volodymyr Fialko <vfialko@marvell.com>
Subject: RE: [EXT] [PATCH 0/2] Add new IPsec test cases
Date: Tue, 22 Feb 2022 19:41:41 +0000	[thread overview]
Message-ID: <CO6PR18MB44846B4B09C3A67FC4C3DF2AD83B9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220218125203.489078-1-vfialko@marvell.com>

Hi Volodymyr,

Could you please rebase this series to current TOT of dpdk-next-crypto?

> Following test cases were added:
> - IPv4 TTL
> - IPv6 hop limit
> - IPv4 L4 checksum in transport mode
> 
> Volodymyr Fialko (2):
>   test/crypto: add TTL and hop limit decrement cases
>   test/crypto: add L4 checksum case for transport mode
> 
>  app/test/test_cryptodev.c                | 44 ++++++++++++++++++++++++
>  app/test/test_cryptodev_security_ipsec.c | 37 ++++++++++++++++++++
>  app/test/test_cryptodev_security_ipsec.h |  1 +
>  3 files changed, 82 insertions(+)
> 
> --
> 2.25.1


  parent reply	other threads:[~2022-02-22 19:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18 12:52 Volodymyr Fialko
2022-02-18 12:52 ` [PATCH 1/2] test/crypto: add TTL and hop limit decrement cases Volodymyr Fialko
2022-02-18 12:52 ` [PATCH 2/2] test/crypto: add L4 checksum case for transport mode Volodymyr Fialko
2022-02-22 19:41 ` Akhil Goyal [this message]
2022-02-23 10:40 ` [PATCH v2 0/2] Add new IPsec test cases Volodymyr Fialko
2022-02-23 10:40   ` [PATCH v2 1/2] test/crypto: add TTL and hop limit decrement cases Volodymyr Fialko
2022-02-23 10:48     ` Akhil Goyal
2022-02-23 10:40   ` [PATCH v2 2/2] test/crypto: add L4 checksum case for transport mode Volodymyr Fialko

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=CO6PR18MB44846B4B09C3A67FC4C3DF2AD83B9@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=vfialko@marvell.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).