DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>,
	"zbigniew.bodek@caviumnetworks.com"
	<zbigniew.bodek@caviumnetworks.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH] examples/ipsec-secgw: add support for SHA256	HMAC
Date: Mon, 16 Jan 2017 19:00:54 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D897476C5C58@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <33fc435a-14fc-3657-d625-a48f043240ad@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Sergio Gonzalez
> Monroy
> Sent: Friday, January 13, 2017 8:52 AM
> To: zbigniew.bodek@caviumnetworks.com; dev@dpdk.org
> Cc: jerin.jacob@caviumnetworks.com
> Subject: Re: [dpdk-dev] [PATCH] examples/ipsec-secgw: add support for
> SHA256 HMAC
> 
> On 12/01/2017 14:52, zbigniew.bodek@caviumnetworks.com wrote:
> > From: Zbigniew Bodek <zbigniew.bodek@caviumnetworks.com>
> >
> > Add minor adjustments to support SHA256 HMAC:
> > - extend maximum key length to match SHA256 HMAC
> > - add SHA256 HMAC parameters and configuration string
> > - add SHA256 HMAC to inbound and outbound cases
> >
> > Signed-off-by: Zbigniew Bodek <zbigniew.bodek@caviumnetworks.com>
> > ---
> 
> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>

Applied to dpdk-next-crypto.
Thanks,

Pablo

      reply	other threads:[~2017-01-16 19:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 14:52 zbigniew.bodek
2017-01-13  8:52 ` Sergio Gonzalez Monroy
2017-01-16 19:00   ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D897476C5C58@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=sergio.gonzalez.monroy@intel.com \
    --cc=zbigniew.bodek@caviumnetworks.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 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).