All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Ruifeng Wang <ruifeng.wang@arm.com>,
	"gavin.hu@arm.com" <gavin.hu@arm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"jerinj@marvell.com" <jerinj@marvell.com>,
	 "honnappa.nagarahalli@arm.com" <honnappa.nagarahalli@arm.com>,
	"nd@arm.com" <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/5] armv8 crypto PMD update
Date: Thu, 23 Jan 2020 13:38:49 +0000	[thread overview]
Message-ID: <VE1PR04MB6639159C9AC6F6892CE5D2BBE60F0@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200123034557.146822-1-ruifeng.wang@arm.com>



> 
> Maintainance of armv8_crypto library created by Marvell/Cavium will
> be discontinued. Going forward, Armv8 crypto PMD will link to AArch64
> crypto library hosted by Arm.
> 
> Patch 1/5, 3/5 update source code and document respectively to reflect
> the change.
> Patch 2/5 adds meson build support for this PMD.
> Patch 5/5 fixs Clang build issue when Armv8 crypto PMD is enabled.
> 
> 
> v3:
> Include meson build support patch.
> Add release notes.
> 
> v2:
> Convert to formal patches from RFC.
> API and public structure renaming.
> 
> Dharmik Thakkar (1):
>   crypto/armv8: enable meson build
> 
> Ruifeng Wang (4):
>   crypto/armv8: link PMD to crypto library hosted by Arm
>   doc: update link to the crypto library for armv8 PMD
>   doc: update release notes for armv8 crypto PMD
>   crypto/armv8: fix clang build
> 
>  doc/guides/cryptodevs/armv8.rst          |  7 ++-
>  doc/guides/rel_notes/release_20_02.rst   |  5 +++
>  drivers/crypto/armv8/Makefile            |  3 +-
>  drivers/crypto/armv8/armv8_pmd_private.h |  4 +-
>  drivers/crypto/armv8/meson.build         | 25 +++++++++++
>  drivers/crypto/armv8/rte_armv8_pmd.c     | 55 ++++++++++++++++--------
>  drivers/crypto/armv8/rte_armv8_pmd_ops.c |  2 -
>  drivers/crypto/meson.build               |  1 +
>  meson_options.txt                        |  2 +
>  mk/rte.app.mk                            |  2 +-
>  10 files changed, 77 insertions(+), 29 deletions(-)
>  create mode 100644 drivers/crypto/armv8/meson.build
> 

Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

Applied to dpdk-next-crypto
Squashed the doc patches to 1/5. As per current protocol no separate patches for doc.

Thanks.


      parent reply	other threads:[~2020-01-23 13:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10  8:28 [dpdk-dev] [RFC PATCH 0/3] armv8 crypto PMD update Ruifeng Wang
2019-12-10  8:28 ` [dpdk-dev] [RFC PATCH 1/3] crypto/armv8: link PMD to crypto library hosted by Arm Ruifeng Wang
2019-12-10  8:28 ` [dpdk-dev] [RFC PATCH 2/3] doc: update link to the crypto library for armv8 PMD Ruifeng Wang
2019-12-10 10:07   ` Jerin Jacob
2019-12-10  8:28 ` [dpdk-dev] [RFC PATCH 3/3] crypto/armv8: fix clang build Ruifeng Wang
2020-01-17 12:11 ` [dpdk-dev] [RFC PATCH 0/3] armv8 crypto PMD update Akhil Goyal
2020-01-17 14:28   ` Ruifeng Wang
2020-01-19  7:40 ` [dpdk-dev] [PATCH v2 " Ruifeng Wang
2020-01-19  7:40   ` [dpdk-dev] [PATCH v2 1/3] crypto/armv8: link PMD to crypto library hosted by Arm Ruifeng Wang
2020-01-19  7:40   ` [dpdk-dev] [PATCH v2 2/3] doc: update link to the crypto library for armv8 PMD Ruifeng Wang
2020-01-19  7:40   ` [dpdk-dev] [PATCH v2 3/3] crypto/armv8: fix clang build Ruifeng Wang
2020-01-21  7:09   ` [dpdk-dev] [PATCH v2 0/3] armv8 crypto PMD update Akhil Goyal
2020-01-21  9:49     ` Ruifeng Wang
2020-01-23  3:45 ` [dpdk-dev] [PATCH v3 0/5] " Ruifeng Wang
2020-01-23  3:45   ` [dpdk-dev] [PATCH v3 1/5] crypto/armv8: link PMD to crypto library hosted by Arm Ruifeng Wang
2020-01-23  3:45   ` [dpdk-dev] [PATCH v3 2/5] crypto/armv8: enable meson build Ruifeng Wang
2020-01-23  3:45   ` [dpdk-dev] [PATCH v3 3/5] doc: update link to the crypto library for armv8 PMD Ruifeng Wang
2020-01-23  3:45   ` [dpdk-dev] [PATCH v3 4/5] doc: update release notes for armv8 crypto PMD Ruifeng Wang
2020-01-23  3:45   ` [dpdk-dev] [PATCH v3 5/5] crypto/armv8: fix clang build Ruifeng Wang
2020-01-23 13:38   ` 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=VE1PR04MB6639159C9AC6F6892CE5D2BBE60F0@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=gavin.hu@arm.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jerinj@marvell.com \
    --cc=nd@arm.com \
    --cc=ruifeng.wang@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.