patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: "michaelsh@marvell.com" <michaelsh@marvell.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"marko.kovacevic@intel.com" <marko.kovacevic@intel.com>,
	"lironh@marvell.com" <lironh@marvell.com>
Subject: Re: [dpdk-stable] [PATCH 0/8] Fips validation fixes
Date: Thu, 19 Sep 2019 13:15:47 +0000	[thread overview]
Message-ID: <DB8PR04MB6635977DA45228D1CAC9282AE6890@DB8PR04MB6635.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20190919121232.4864-1-michaelsh@marvell.com>

Hi Michael,

I see that there are compilation issues with meson build
Please check http://mails.dpdk.org/archives/test-report/2019-September/098161.html

Also run devtools/check-git-log.sh -<number of patches>.

You should have a fixes line in each of the fix commits as stated earlier also.
Please have a look at http://doc.dpdk.org/guides/contributing/patches.html for any clarification.

Thanks,
Akhil

> -----Original Message-----
> From: michaelsh@marvell.com <michaelsh@marvell.com>
> Sent: Thursday, September 19, 2019 5:42 PM
> To: Akhil Goyal <akhil.goyal@nxp.com>
> Cc: stable@dpdk.org; dev@dpdk.org; marko.kovacevic@intel.com;
> lironh@marvell.com; michaelsh@marvell.com
> Subject: [PATCH 0/8] Fips validation fixes
> 
> From: Michael Shamis <michaelsh@marvell.com>
> 
> Include fixes related to SHA, TDES and GCM.
> 
> Michael Shamis (8):
>   examples/fips_validation: separation between HMAC-SHA and SHA
>   examples/fips_validation: fix structs used for AES-GCM
>   examples/fips_validation: initialize IV for AES-GCM
>   examples/fips_validation: move digest after cipher text
>   examples/fips_validation: fix AES-GCM decryption vector
>   examples/fips_validation: fix overwrite of KEY line in TDES
>   examples/fips_validation: improve algo parsing logic
>   examples/fips_validation: fix plain text overwrite
> 
>  examples/fips_validation/fips_validation.c    | 85 +++++++++++++++++--
>  .../fips_validation/fips_validation_gcm.c     | 39 +++++++--
>  examples/fips_validation/main.c               | 15 +++-
>  3 files changed, 119 insertions(+), 20 deletions(-)
> 
> --
> 2.23.0


      parent reply	other threads:[~2019-09-19 13:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 12:12 michaelsh
2019-09-19 12:12 ` [dpdk-stable] [PATCH 1/8] examples/fips_validation: separation between HMAC-SHA and SHA michaelsh
2019-09-19 12:12 ` [dpdk-stable] [PATCH 2/8] examples/fips_validation: fix structs used for AES-GCM michaelsh
2019-09-19 12:12 ` [dpdk-stable] [PATCH 3/8] examples/fips_validation: initialize IV " michaelsh
2019-09-19 12:12 ` [dpdk-stable] [PATCH 4/8] examples/fips_validation: move digest after cipher text michaelsh
2019-09-19 12:12 ` [dpdk-stable] [PATCH 5/8] examples/fips_validation: fix AES-GCM decryption vector michaelsh
2019-09-19 12:12 ` [dpdk-stable] [PATCH 6/8] examples/fips_validation: fix overwrite of KEY line in TDES michaelsh
2019-09-19 12:12 ` [dpdk-stable] [PATCH 7/8] examples/fips_validation: improve algo parsing logic michaelsh
2019-09-19 12:12 ` [dpdk-stable] [PATCH 8/8] examples/fips_validation: fix plain text overwrite michaelsh
2019-09-19 13:15 ` 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=DB8PR04MB6635977DA45228D1CAC9282AE6890@DB8PR04MB6635.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=lironh@marvell.com \
    --cc=marko.kovacevic@intel.com \
    --cc=michaelsh@marvell.com \
    --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).