From: Anoob Joseph <anoobj@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>,
Shijith Thotton <sthotton@marvell.com>
Subject: RE: [PATCH v2 0/3] app/testseventdev: crypto producer fixes
Date: Mon, 7 Nov 2022 11:01:10 +0000 [thread overview]
Message-ID: <PH0PR18MB46724A7B87ABAF3D921FC4E6DF3C9@PH0PR18MB4672.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20221104122556.751286-1-vfialko@marvell.com>
>
> This patch series address issues with crypto producer - correct setup
> sequence and multi stage handling with time stamp attached.
>
> v2:
> - Split fixes into individual patches
>
> Volodymyr Fialko (3):
> app/testeventdev: setup crypto adapter before sessions
> app/testeventdev: fix asymmetric last stage handling
> app/testeventdev: fix timestamp with crypto producer
>
Series Acked-by: Anoob Joseph <anoobj@marvell.com>
next prev parent reply other threads:[~2022-11-07 11:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 17:53 [PATCH 0/2] " Volodymyr Fialko
2022-11-03 17:53 ` [PATCH 1/2] app/testeventdev: setup crypto adapter before sessions Volodymyr Fialko
2022-11-03 17:53 ` [PATCH 2/2] app/testeventdev: resolve issues with crypto producer Volodymyr Fialko
2022-11-04 8:44 ` Jerin Jacob
2022-11-04 4:29 ` [PATCH 0/2] app/testseventdev: crypto producer fixes Anoob Joseph
2022-11-04 12:25 ` [PATCH v2 0/3] " Volodymyr Fialko
2022-11-04 12:25 ` [PATCH v2 1/3] app/testeventdev: setup crypto adapter before sessions Volodymyr Fialko
2022-11-04 12:25 ` [PATCH v2 2/3] app/testeventdev: fix asymmetric last stage handling Volodymyr Fialko
2022-11-04 12:25 ` [PATCH v2 3/3] app/testeventdev: fix timestamp with crypto producer Volodymyr Fialko
2022-11-07 11:01 ` Anoob Joseph [this message]
2022-11-07 18:14 ` [PATCH v2 0/3] app/testseventdev: crypto producer fixes Jerin Jacob
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=PH0PR18MB46724A7B87ABAF3D921FC4E6DF3C9@PH0PR18MB4672.namprd18.prod.outlook.com \
--to=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=sthotton@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).