From: "Ji, Kai" <kai.ji@intel.com>
To: Akhil Goyal <gakhil@marvell.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"g.singh@nxp.com" <g.singh@nxp.com>
Subject: Re: [dpdk-dev] [EXT] [dpdk-dev v1] test/crypto: maxlen calculation update
Date: Fri, 8 Oct 2021 11:40:10 +0000 [thread overview]
Message-ID: <DM6PR11MB3403FA94749821E00579C98C81B29@DM6PR11MB3403.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB4484BAC38A174D3115876082D8B19@CO6PR18MB4484.namprd18.prod.outlook.com>
Hi Akhil,
I just update the v2: http://patchwork.dpdk.org/project/dpdk/patch/20211008113345.31818-1-kai.ji@intel.com/
This patch is a generic fix of test case for SGL op, I think there is no dependence with Hemant's patch.
Regards
Kai
> -----Original Message-----
> From: Akhil Goyal <gakhil@marvell.com>
> Sent: Thursday, October 7, 2021 4:20 PM
> To: Zhang, Roy Fan <roy.fan.zhang@intel.com>; Ji, Kai <kai.ji@intel.com>;
> dev@dpdk.org
> Cc: hemant.agrawal@nxp.com; g.singh@nxp.com
> Subject: RE: [EXT] [dpdk-dev] [dpdk-dev v1] test/crypto: maxlen calculation
> update
>
> > Sorry didn't catch you are mentioning this part - yes we have been
> > preparing for adding oop support into qat for a while :-). Rebecca has
> > already tested and acked the patchset. We are waiting for you merging
> > them before rebasing.
> >
> I am expecting a new patchset from Hemant to handle Konstantin's
> comments.
next prev parent reply other threads:[~2021-10-08 11:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 15:38 [dpdk-dev] " Kai Ji
2021-09-30 9:43 ` [dpdk-dev] FW: " Zhang, Roy Fan
2021-10-07 12:46 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-10-07 13:54 ` Zhang, Roy Fan
2021-10-07 13:59 ` Akhil Goyal
2021-10-07 14:34 ` Zhang, Roy Fan
2021-10-07 15:20 ` Akhil Goyal
2021-10-07 15:43 ` Zhang, Roy Fan
2021-10-08 11:40 ` Ji, Kai [this message]
2021-10-08 11:33 ` [dpdk-dev] [dpdk-dev v2] " Kai Ji
2021-10-31 19:26 ` [dpdk-dev] [EXT] " 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=DM6PR11MB3403FA94749821E00579C98C81B29@DM6PR11MB3403.namprd11.prod.outlook.com \
--to=kai.ji@intel.com \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.com \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=roy.fan.zhang@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).