From: Tal Shnaiderman <talshn@nvidia.com>
To: Akhil Goyal <gakhil@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
Cc: "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>,
"declan.doherty@intel.com" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [EXT] [PATCH] cryptodev: build on Windows
Date: Tue, 5 Oct 2021 12:12:32 +0000 [thread overview]
Message-ID: <DM4PR12MB53897FA8484732241F8F87B1A4AF9@DM4PR12MB5389.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB44843D47AECECACEF90BB5E6D8AF9@CO6PR18MB4484.namprd18.prod.outlook.com>
> Subject: RE: [EXT] [PATCH] cryptodev: build on Windows
>
> External email: Use caution opening links or attachments
>
>
> > > Build the cryptography device library on Windows OS by removing
> > > unneeded include and exports blocking the compilation.
> > >
> > > Signed-off-by: Tal Shnaiderman <talshn@nvidia.com>
> > > ---
> > Acked-by: Akhil Goyal <gakhil@marvell.com>
> >
> > Applied to dpdk-next-crypto
> Removing this patch from dpdk-next-crypto as the patch is superseded With
> another series delegated to Thomas.
> http://patches.dpdk.org/project/dpdk/cover/20211002003344.594-1-
> u9012063@gmail.com/
>
> Please ensure previous versions are marked superseded or else it will create
> Unnecessary issues while merging.
>
>
Thanks, you're right, I superseded the security patches but didn't notice a v3 for crypto was also sent.
prev parent reply other threads:[~2021-10-05 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 17:16 [dpdk-dev] " Tal Shnaiderman
2021-09-19 14:03 ` William Tu
2021-09-23 18:07 ` Kadam, Pallavi
2021-10-05 10:39 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-10-05 10:50 ` Akhil Goyal
2021-10-05 12:12 ` Tal Shnaiderman [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=DM4PR12MB53897FA8484732241F8F87B1A4AF9@DM4PR12MB5389.namprd12.prod.outlook.com \
--to=talshn@nvidia.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=gakhil@marvell.com \
--cc=navasile@linux.microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=thomas@monjalon.net \
/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).