From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
Tomasz Duszynski <tdu@semihalf.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "mw@semihalf.com" <mw@semihalf.com>,
"dima@marvell.com" <dima@marvell.com>,
"nsamsono@marvell.com" <nsamsono@marvell.com>,
"jianbo.liu@arm.com" <jianbo.liu@arm.com>
Subject: Re: [dpdk-dev] [PATCH v3 1/2] crypto/mrvl: sync compilation with musdk-17.10
Date: Tue, 16 Jan 2018 17:54:32 +0000 [thread overview]
Message-ID: <55484d6a-2f18-4973-74ef-f7fb7425f57d@intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8976CC6AC83@IRSMSX108.ger.corp.intel.com>
On 1/9/2018 11:47 AM, De Lara Guarch, Pablo wrote:
>
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Tomasz Duszynski
>> Sent: Tuesday, January 9, 2018 9:09 AM
>> To: dev@dpdk.org
>> Cc: mw@semihalf.com; dima@marvell.com; nsamsono@marvell.com;
>> jianbo.liu@arm.com; Tomasz Duszynski <tdu@semihalf.com>
>> Subject: [dpdk-dev] [PATCH v3 1/2] crypto/mrvl: sync compilation with
>> musdk-17.10
>>
>> 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>
>
> Applied to dpdk-next-crypto.
Hi Pablo,
Would you be OK if I get this specific patch to the next-net? And merge with net
counterpart of it [1].
Because when net and crypto versions are separate patches, one of them is
causing build error for a specific version of musdk.
When musdk version is updated, both net and crypto should be updated atomically
for that new version.
[1]
https://dpdk.org/dev/patchwork/patch/31927/
> Thanks,
>
> Pablo
>
next prev parent reply other threads:[~2018-01-16 17:54 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
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 [this message]
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=55484d6a-2f18-4973-74ef-f7fb7425f57d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=dima@marvell.com \
--cc=jianbo.liu@arm.com \
--cc=mw@semihalf.com \
--cc=nsamsono@marvell.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=tdu@semihalf.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).