From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Tomasz Duszynski <tdu@semihalf.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "mw@semihalf.com" <mw@semihalf.com>,
"jck@semihalf.com" <jck@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 2/2] crypto/mrvl: update MRVL CRYPTO PMD documentation
Date: Mon, 11 Dec 2017 12:44:43 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC5928F@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1512048774-23838-3-git-send-email-tdu@semihalf.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Tomasz Duszynski
> Sent: Thursday, November 30, 2017 1:33 PM
> 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: [dpdk-dev] [PATCH 2/2] crypto/mrvl: update MRVL CRYPTO PMD
> documentation
>
> Update MRVL CRYPTO PMD documentation.
>
> Signed-off-by: Tomasz Duszynski <tdu@semihalf.com>
This is depending on the network driver update, right?
You should say it in the cover letter. I will wait until it is applied then.
...
> -
> Installation
> ------------
>
> @@ -92,20 +85,11 @@ Currently there are two driver specific compilation
> options in
>
> Toggle display of debugging messages.
>
> -During compilation external MUSDK library, which provides direct access -
> to Marvell's EIP197 cryptographic engine, is necessary. Library sources are -
> available `here <https://github.com/MarvellEmbeddedProcessors/musdk-
> marvell/tree/musdk-armada-17.08>`__.
> +For a list of prerequisites please refer to `Prerequisites` section in
> +:ref:`MRVL Poll Mode Driver <mrvl_poll_mode_driver>` guide.
Maybe say that it is the network PMD?
Thanks,
Pablo
next prev parent reply other threads:[~2017-12-11 12:44 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 [this message]
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
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=E115CCD9D858EF4F90C690B0DCB4D8976CC5928F@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.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 \
--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).