From: Akhil Goyal <gakhil@marvell.com>
To: Ruifeng Wang <Ruifeng.Wang@arm.com>,
"jspewock@iol.unh.edu" <jspewock@iol.unh.edu>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "bernard.iremonger@intel.com" <bernard.iremonger@intel.com>,
"juraj.linkes@pantheon.tech" <juraj.linkes@pantheon.tech>,
"ohilyard@iol.unh.edu" <ohilyard@iol.unh.edu>,
"stable@dpdk.org" <stable@dpdk.org>, nd <nd@arm.com>
Subject: RE: [PATCH] test/ipsec: fix invalid crypto device failing
Date: Fri, 26 Aug 2022 12:12:49 +0000 [thread overview]
Message-ID: <CO6PR18MB44845A7FE00F71685375EC12D8759@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <AS8PR08MB70808C0D23D21A1BF96725609E9F9@AS8PR08MB7080.eurprd08.prod.outlook.com>
> > From: Jeremy Spewock <jspewock@iol.unh.edu>
> >
> > ipsec_autotest is now skipped if no compatible crypto devices are found.
> >
> > Fixes issue where if at least one crypto device was found but no
> > compatible crypto devices for the ipsec_autotest test case are present
> > the case would fail with no error message. Now, when this situation is
> > encountered, the test case will be skipped with an explanation.
> >
> > Fixes: 59d7353b0df0 ("test/ipsec: fix test suite setup")
> >
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Jeremy Spewock <jspewock@iol.unh.edu>
> > Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
>
Applied to dpdk-next-crypto
prev parent reply other threads:[~2022-08-26 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 14:17 jspewock
2022-08-04 8:27 ` Ruifeng Wang
2022-08-26 12:12 ` Akhil Goyal [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=CO6PR18MB44845A7FE00F71685375EC12D8759@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=Ruifeng.Wang@arm.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--cc=nd@arm.com \
--cc=ohilyard@iol.unh.edu \
--cc=stable@dpdk.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).