From: Tomasz Duszynski <tdu@semihalf.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: Tomasz Duszynski <tdu@semihalf.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"dima@marvell.com" <dima@marvell.com>,
"nsamsono@marvell.com" <nsamsono@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/mrvl: add MRVL PMD to meson
Date: Thu, 19 Apr 2018 13:40:23 +0200 [thread overview]
Message-ID: <20180419114023.GA14206@sh> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8976CCD82F7@IRSMSX108.ger.corp.intel.com>
On Thu, Apr 19, 2018 at 11:31:54AM +0000, De Lara Guarch, Pablo wrote:
> Hi Tomasz,
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Tomasz Duszynski
> > Sent: Monday, April 16, 2018 7:08 AM
> > To: dev@dpdk.org
> > Cc: Richardson, Bruce <bruce.richardson@intel.com>; dima@marvell.com;
> > nsamsono@marvell.com; Tomasz Duszynski <tdu@semihalf.com>
> > Subject: [dpdk-dev] [PATCH] crypto/mrvl: add MRVL PMD to meson
> >
> > Add MRVL CRYPTO PMD to meson build system.
> >
> > Signed-off-by: Tomasz Duszynski <tdu@semihalf.com>
>
> Could you make the same change that you made in the network driver into this patch?
> Bruce will get this patch, as he has already applied the network driver patch, which will be a dependency of this one.
>
> Thanks,
> Pablo
You mean this one http://dpdk.org/dev/patchwork/patch/38488/?
Frankly speaking I have a crypto patch but since I did not see any comments
from Bruce regarding net I postponed it.
--
- Tomasz Duszyński
next prev parent reply other threads:[~2018-04-19 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 6:07 Tomasz Duszynski
2018-04-19 11:31 ` De Lara Guarch, Pablo
2018-04-19 11:40 ` Tomasz Duszynski [this message]
2018-04-19 12:08 ` Bruce Richardson
2018-04-19 12:21 ` [dpdk-dev] [PATCH v2] " Tomasz Duszynski
2018-04-19 13:36 ` Bruce Richardson
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=20180419114023.GA14206@sh \
--to=tdu@semihalf.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dima@marvell.com \
--cc=nsamsono@marvell.com \
--cc=pablo.de.lara.guarch@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).