From: Luca Boccassi <bluca@debian.org>
To: Hari Kumar Vemula <hari.kumarx.vemula@intel.com>, dev@dpdk.org
Cc: bruce.richardson@intel.com, reshma.pattan@intel.com,
declan.doherty@intel.com, pablo.de.lara.guarch@intel.com
Subject: Re: [dpdk-dev] [PATCH v2 0/4] enable meson support for aesni_gcm, aesni_mb, kasumi and zuc
Date: Fri, 05 Oct 2018 12:13:28 +0100 [thread overview]
Message-ID: <1538738008.8721.7.camel@debian.org> (raw)
In-Reply-To: <1538737157-4807-1-git-send-email-hari.kumarx.vemula@intel.com>
On Fri, 2018-10-05 at 11:59 +0100, Hari Kumar Vemula wrote:
> 1/4: enablement of aesni_gcm pmd in meson
> 2/4: enablement of aesni_mb pmd in meson
> 3/4: enablement of kasumi pmd enable in meson
> 4/4: enablement of zuc pmd enable in meson
>
> --
> v2: Removed lib dependancy options from meson_option.txt file
> --
>
>
> Hari Kumar Vemula (4):
> drivers/crypto: enable meson support for the aesni gcm
> drivers/crypto: enable meson support for the aesni mb
> drivers/crypto: enable meson support for the kasumi
> drivers/crypto: enable meson support for the zuc
>
> drivers/crypto/aesni_gcm/meson.build | 13 +++++++++++++
> drivers/crypto/aesni_mb/meson.build | 12 ++++++++++++
> drivers/crypto/kasumi/meson.build | 12 ++++++++++++
> drivers/crypto/meson.build | 4 ++--
> drivers/crypto/zuc/meson.build | 12 ++++++++++++
> 5 files changed, 51 insertions(+), 2 deletions(-)
> create mode 100644 drivers/crypto/aesni_gcm/meson.build
> create mode 100644 drivers/crypto/aesni_mb/meson.build
> create mode 100644 drivers/crypto/kasumi/meson.build
> create mode 100644 drivers/crypto/zuc/meson.build
Series-acked-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2018-10-05 11:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 12:00 [dpdk-dev] [PATCH " Hari Kumar Vemula
2018-09-29 12:00 ` [dpdk-dev] [PATCH 1/4] driver/crypto: enable meson support for the aesni gcm Hari Kumar Vemula
2018-10-01 9:31 ` Bruce Richardson
2018-09-29 12:00 ` [dpdk-dev] [PATCH 2/4] drivers/crypto: enable meson support for the aesni mb Hari Kumar Vemula
2018-09-29 12:01 ` [dpdk-dev] [PATCH 3/4] drivers/crypto: enable meson support for the kasumi Hari Kumar Vemula
2018-09-29 12:01 ` [dpdk-dev] [PATCH 4/4] drivers/crypto: enable meson support for the zuc Hari Kumar Vemula
2018-09-30 10:01 ` [dpdk-dev] [PATCH 0/4] enable meson support for aesni_gcm, aesni_mb, kasumi and zuc Luca Boccassi
2018-10-01 9:36 ` Bruce Richardson
2018-10-05 10:59 ` [dpdk-dev] [PATCH v2 " Hari Kumar Vemula
2018-10-05 11:13 ` Luca Boccassi [this message]
2018-10-09 12:41 ` Akhil Goyal
2018-10-05 10:59 ` [dpdk-dev] [PATCH v2 1/4] drivers/crypto: enable meson support for the aesni gcm Hari Kumar Vemula
2018-10-05 10:59 ` [dpdk-dev] [PATCH v2 2/4] drivers/crypto: enable meson support for the aesni mb Hari Kumar Vemula
2018-10-05 10:59 ` [dpdk-dev] [PATCH v2 3/4] drivers/crypto: enable meson support for the kasumi Hari Kumar Vemula
2018-10-05 10:59 ` [dpdk-dev] [PATCH v2 4/4] drivers/crypto: enable meson support for the zuc Hari Kumar Vemula
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=1538738008.8721.7.camel@debian.org \
--to=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=hari.kumarx.vemula@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=reshma.pattan@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).