DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: "marko.kovacevic@intel.com" <marko.kovacevic@intel.com>,
	"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>
Cc: "anoobj@marvell.com" <anoobj@marvell.com>,
	"pathreya@marvell.com" <pathreya@marvell.com>,
	"ayverma@marvell.com" <ayverma@marvell.com>,
	"kkotamarthy@marvell.com" <kkotamarthy@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>,
	Archana Muniganti <marchana@marvell.com>
Subject: Re: [dpdk-dev] [PATCH 1/3] examples/fips_validation: fix TDES interim callback
Date: Thu, 2 Jul 2020 18:53:37 +0000	[thread overview]
Message-ID: <VI1PR04MB3168CD41CBF8A84096D3E8D2E66D0@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1591883057-11008-1-git-send-email-marchana@marvell.com>

Hi Marko/Fan,

Could you please review this series?

> Subject: [PATCH 1/3] examples/fips_validation: fix TDES interim callback
> 
> Fix missing callback registration and the incorrect
> callback definition for interim NK_STR. The callback
> should compare input key against the interim.
> 
> Fixes: 527cbf3d5ee3 ("examples/fips_validation: support TDES parsing")
> 
> Signed-off-by: Archana Muniganti <marchana@marvell.com>

-Akhil

  parent reply	other threads:[~2020-07-02 18:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 13:44 Archana Muniganti
2020-06-11 13:44 ` [dpdk-dev] [PATCH 2/3] examples/fips_validation: fix parsing of TDES vectors Archana Muniganti
2020-06-11 13:44 ` [dpdk-dev] [PATCH 3/3] examples/fips_validation: fix overwrite of COUNT for " Archana Muniganti
2020-07-02 18:53 ` Akhil Goyal [this message]
2020-07-12 23:39   ` [dpdk-dev] [PATCH 1/3] examples/fips_validation: fix TDES interim callback Thomas Monjalon
2020-07-15 20:00     ` Akhil Goyal

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=VI1PR04MB3168CD41CBF8A84096D3E8D2E66D0@VI1PR04MB3168.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=ayverma@marvell.com \
    --cc=dev@dpdk.org \
    --cc=kkotamarthy@marvell.com \
    --cc=marchana@marvell.com \
    --cc=marko.kovacevic@intel.com \
    --cc=pathreya@marvell.com \
    --cc=roy.fan.zhang@intel.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).