From: Thomas Monjalon <thomas@monjalon.net>
To: Tal Shnaiderman <talshn@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"pallavi.kadam@intel.com" <pallavi.kadam@intel.com>,
"dmitry.kozliuk@gmail.com" <dmitry.kozliuk@gmail.com>,
"navasile@linux.microsoft.com" <navasile@linux.microsoft.com>,
"dmitrym@microsoft.com" <dmitrym@microsoft.com>,
"jizh@linux.microsoft.com" <jizh@linux.microsoft.com>,
"aconole@redhat.com" <aconole@redhat.com>,
Akhil Goyal <gakhil@marvell.com>
Subject: Re: [dpdk-dev] [EXT] [PATCH] app/test: enable crypto unit tests on Windows
Date: Tue, 08 Feb 2022 14:33:40 +0100 [thread overview]
Message-ID: <8890307.CDJkKcVGEf@thomas> (raw)
In-Reply-To: <CO6PR18MB44841A35DD57B46922C32852D8AF9@CO6PR18MB4484.namprd18.prod.outlook.com>
05/10/2021 15:52, Akhil Goyal:
> > Enable cryptography unit tests on Windows supported crypto PMDs.
> >
> > Signed-off-by: Tal Shnaiderman <talshn@nvidia.com>
> > ---
> > Depends-on: series-18674 ("app/test: enable subset of tests on Windows")
> > Depends-on: patch-98942 ("security: build on Windows")
> > ---
> Acked-by: Akhil Goyal <gakhil@marvell.com>
>
> Delegating this patch to Thomas, as dependent series are delegated to Thomas as well.
The dependencies are merged but I am not sure something is required
to enable crypto unit tests on Windows.
Please check what was done during the latest reworks.
prev parent reply other threads:[~2022-02-08 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 17:16 [dpdk-dev] [PATCH] app/test: enable crypto unit tests on Windows Tal Shnaiderman
2021-10-05 13:52 ` [dpdk-dev] [EXT] " Akhil Goyal
2022-02-08 13:33 ` Thomas Monjalon [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=8890307.CDJkKcVGEf@thomas \
--to=thomas@monjalon.net \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=gakhil@marvell.com \
--cc=jizh@linux.microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=talshn@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.