From: Thomas Monjalon <thomas@monjalon.net>
To: "Kovacevic, Marko" <marko.kovacevic@intel.com>
Cc: dev@dpdk.org, pablo.de.lara.guarch@intel.com, deepak.k.jain@intel.com
Subject: Re: [dpdk-dev] [PATCH v1] crypto/aesni_mb: support AES CMAC
Date: Sat, 31 Mar 2018 15:34:50 +0200 [thread overview]
Message-ID: <3945769.K91UHaxDIG@xps> (raw)
In-Reply-To: <20180327121532.44585-1-marko.kovacevic@intel.com>
27/03/2018 14:15, Kovacevic, Marko:
> From: Marko Kovacevic <marko.kovacevic@intel.com>
>
> Signed-off-by: Marko Kovacevic <marko.kovacevic@intel.com>
No comment at all?
Is it a new feature in the IPsec Multi-buffer lib v0.49?
next prev parent reply other threads:[~2018-04-02 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 12:15 Kovacevic, Marko
2018-03-30 15:29 ` De Lara Guarch, Pablo
2018-03-30 15:41 ` De Lara Guarch, Pablo
2018-03-31 13:34 ` Thomas Monjalon [this message]
2018-04-03 13:31 ` [dpdk-dev] [PATCH v2] " Kovacevic, Marko
2018-04-04 12:33 ` De Lara Guarch, Pablo
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=3945769.K91UHaxDIG@xps \
--to=thomas@monjalon.net \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=marko.kovacevic@intel.com \
--cc=pablo.de.lara.guarch@intel.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).