From: Luca Boccassi <bluca@debian.org>
To: "Ji, Kai" <kai.ji@intel.com>, dpdk stable <stable@dpdk.org>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"Jiang, YuX" <yux.jiang@intel.com>,
"ktraynor@redhat.com" <ktraynor@redhat.com>
Subject: Re: FW: [PATCH 21.11.1 v2] test/crypto: skip oop test for raw api
Date: Wed, 17 Aug 2022 10:26:38 +0100 [thread overview]
Message-ID: <512d47f3d899530dc3748b5092539f2e961b2db2.camel@debian.org> (raw)
In-Reply-To: <SN6PR11MB340833A2684996F8A13CE8FE816B9@SN6PR11MB3408.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
On Tue, 2022-08-16 at 14:43 +0000, Ji, Kai wrote:
>
> > -----Original Message-----
> > From: Ji, Kai
> > Sent: Monday, July 25, 2022 12:44 PM
> > To: ktraynor@redhat.com
> > Cc: hemant.agrawal@nxp.com; Poczatek, Jakub
> > <jakub.poczatek@intel.com>; Jiang, YuX <YuX.Jiang@intel.com>
> > Subject: [PATCH 21.11.1 v2] test/crypto: skip oop test for raw api
> >
> > Hi Kevin,
> >
> > The attached patch fix a single failing oop test in raw api where it supposed to
> > be skipped, and this test also failed in next-crypto 21.11 release.
> > Because of major qat data-path refactor has been included in next-crypto
> > 22.03 release, this test is passing now as the OOP feature is supported by
> > refactor.
> >
> > So I didn't include upstream commit id in this patch as I'm not sure the fix will
> > be needed for the next-crypto anymore.
> >
> > Can you check to see if this patch is qualified to be merged into LTS 21.11.1 v2?
> >
> > Regards
> >
> > Kai
Thanks, applied and pushed. Next time please send it directly to
stable@dpdk.org rather than to the maintainer privately.
--
Kind regards,
Luca Boccassi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-08-17 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SN6PR11MB34085D01DE954E295442DE5081959@SN6PR11MB3408.namprd11.prod.outlook.com>
2022-08-16 14:43 ` Ji, Kai
2022-08-17 9:26 ` Luca Boccassi [this message]
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=512d47f3d899530dc3748b5092539f2e961b2db2.camel@debian.org \
--to=bluca@debian.org \
--cc=hemant.agrawal@nxp.com \
--cc=kai.ji@intel.com \
--cc=ktraynor@redhat.com \
--cc=stable@dpdk.org \
--cc=yux.jiang@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).