All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>,
	"Trahe, Fiona" <fiona.trahe@intel.com>,
	 "Dybkowski, AdamX" <adamx.dybkowski@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] test/crypto: replace wireless algos test vectors
Date: Thu, 2 Apr 2020 12:37:10 +0000	[thread overview]
Message-ID: <MWHPR1101MB2158E04C4260503549980823FCC60@MWHPR1101MB2158.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DB8PR04MB663598170641097DEADA81F1E6C90@DB8PR04MB6635.eurprd04.prod.outlook.com>



> -----Original Message-----
> From: Akhil Goyal <akhil.goyal@nxp.com>
> Sent: Wednesday, April 1, 2020 3:15 PM
> To: Trahe, Fiona <fiona.trahe@intel.com>; Dybkowski, AdamX
> <adamx.dybkowski@intel.com>; Thomas Monjalon <thomas@monjalon.net>
> Cc: dev@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>
> Subject: RE: [dpdk-dev] [PATCH] test/crypto: replace wireless algos test
> vectors
> 
> Hi Fiona,
> 
> > Hi Akhil, Thomas,
> > Can you please hold off on applying this patch for the moment - it
> > seems we may get approval on licensing for the original vectors.
> > Fiona
> >
> Do we still need this patch?

Hi Akhil,

We are still waiting for ETSI approval for using the test vectors. I'd suggest postponing/superseding this patchset in this release. We can bring it back if we don't get approval.

John



      reply	other threads:[~2020-04-02 12:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 11:24 [dpdk-dev] [PATCH] test/crypto: replace wireless algos test vectors Adam Dybkowski
2020-02-07  9:29 ` Trahe, Fiona
2020-02-12 13:23 ` Akhil Goyal
2020-02-13 13:44   ` Dybkowski, AdamX
2020-02-17 10:49     ` Trahe, Fiona
2020-04-01 14:14       ` Akhil Goyal
2020-04-02 12:37         ` Mcnamara, John [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=MWHPR1101MB2158E04C4260503549980823FCC60@MWHPR1101MB2158.namprd11.prod.outlook.com \
    --to=john.mcnamara@intel.com \
    --cc=adamx.dybkowski@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@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 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.