From: Tomasz Duszynski <tdu@semihalf.com>
To: dev@dpdk.org
Cc: mw@semihalf.com, jck@semihalf.com, dima@marvell.com,
nsamsono@marvell.com, jianbo.liu@arm.com,
Tomasz Duszynski <tdu@semihalf.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] crypto/mrvl: sync compilation with musdk-17.10
Date: Mon, 8 Jan 2018 15:27:52 +0100 [thread overview]
Message-ID: <20180108142752.GA8186@sh.semihalf.local> (raw)
In-Reply-To: <1513001223-9881-2-git-send-email-tdu@semihalf.com>
On Mon, Dec 11, 2017 at 03:07:02PM +0100, Tomasz Duszynski wrote:
> With a new version of the musdk library it's no longer necessary to
> explicitly define MVCONF_ARCH_DMA_ADDR_T_64BIT.
>
> Proper defines are autogenerated by ./configure script based on
> passed options and available after mv_autogen_comp_flags.h inclusion.
>
> Signed-off-by: Tomasz Duszynski <tdu@semihalf.com>
> Acked-by: Jianbo Liu <jianbo.liu@arm.com>
> ---
> drivers/crypto/mrvl/Makefile | 3 ++-
> drivers/crypto/mrvl/rte_mrvl_compat.h | 1 +
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/mrvl/Makefile b/drivers/crypto/mrvl/Makefile
> index 3532f7c..5515b40 100644
> --- a/drivers/crypto/mrvl/Makefile
> +++ b/drivers/crypto/mrvl/Makefile
> @@ -47,7 +47,8 @@ LIB = librte_pmd_mrvl_crypto.a
> CFLAGS += -O3
> CFLAGS += $(WERROR_FLAGS)
> CFLAGS += -I$(LIBMUSDK_PATH)/include
> -CFLAGS += -DMVCONF_ARCH_DMA_ADDR_T_64BIT
> +CFLAGS += -DMVCONF_TYPES_PUBLIC
> +CFLAGS += -DMVCONF_DMA_PHYS_ADDR_T_PUBLIC
>
> # library version
> LIBABIVER := 1
> diff --git a/drivers/crypto/mrvl/rte_mrvl_compat.h b/drivers/crypto/mrvl/rte_mrvl_compat.h
> index c29fa10..22cd184 100644
> --- a/drivers/crypto/mrvl/rte_mrvl_compat.h
> +++ b/drivers/crypto/mrvl/rte_mrvl_compat.h
> @@ -43,6 +43,7 @@
> #ifdef container_of
> #undef container_of
> #endif
> +#include "env/mv_autogen_comp_flags.h"
> #include "drivers/mv_sam.h"
> #include "drivers/mv_sam_cio.h"
> #include "drivers/mv_sam_session.h"
> --
> 2.7.4
>
This patch has been available here for some time already and it looks it
has not been picked up yet. Should I respin the series?
--
- Tomasz Duszyński
next prev parent reply other threads:[~2018-01-08 14:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 13:32 [dpdk-dev] [PATCH 0/2] Sync compilation with MUSDK-17.10 Tomasz Duszynski
2017-11-30 13:32 ` [dpdk-dev] [PATCH 1/2] crypto/mrvl: sync compilation with musdk-17.10 Tomasz Duszynski
2017-11-30 13:32 ` [dpdk-dev] [PATCH 2/2] crypto/mrvl: update MRVL CRYPTO PMD documentation Tomasz Duszynski
2017-12-11 12:44 ` De Lara Guarch, Pablo
2017-12-11 13:42 ` Tomasz Duszynski
2017-12-04 2:27 ` [dpdk-dev] [PATCH 0/2] Sync compilation with MUSDK-17.10 Jianbo Liu
2017-12-11 14:07 ` [dpdk-dev] [PATCH v2 " Tomasz Duszynski
2017-12-11 14:07 ` [dpdk-dev] [PATCH v2 1/2] crypto/mrvl: sync compilation with musdk-17.10 Tomasz Duszynski
2018-01-08 14:27 ` Tomasz Duszynski [this message]
2018-01-08 14:41 ` De Lara Guarch, Pablo
2018-01-08 14:45 ` Tomasz Duszynski
2018-01-09 9:08 ` [dpdk-dev] [PATCH v3 " Tomasz Duszynski
2018-01-09 9:08 ` [dpdk-dev] [PATCH v3 2/2] crypto/mrvl: update MRVL CRYPTO PMD documentation Tomasz Duszynski
2018-01-09 11:47 ` De Lara Guarch, Pablo
2018-01-09 11:47 ` [dpdk-dev] [PATCH v3 1/2] crypto/mrvl: sync compilation with musdk-17.10 De Lara Guarch, Pablo
2018-01-16 17:54 ` Ferruh Yigit
2017-12-11 14:07 ` [dpdk-dev] [PATCH v2 2/2] crypto/mrvl: update MRVL CRYPTO PMD documentation Tomasz Duszynski
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=20180108142752.GA8186@sh.semihalf.local \
--to=tdu@semihalf.com \
--cc=dev@dpdk.org \
--cc=dima@marvell.com \
--cc=jck@semihalf.com \
--cc=jianbo.liu@arm.com \
--cc=mw@semihalf.com \
--cc=nsamsono@marvell.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).