From: Bruce Richardson <bruce.richardson@intel.com>
To: Tomasz Duszynski <tdu@semihalf.com>
Cc: dev@dpdk.org, jck@semihalf.com, dima@marvell.com,
nsamsono@marvell.com, jianbo.liu@arm.com
Subject: Re: [dpdk-dev] [PATCH 0/2] add MRVL MVPP2 PMD to meson
Date: Fri, 13 Apr 2018 17:14:28 +0100 [thread overview]
Message-ID: <20180413161428.GC37024@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20180413161219.GB37024@bricha3-MOBL.ger.corp.intel.com>
On Fri, Apr 13, 2018 at 05:12:19PM +0100, Bruce Richardson wrote:
> On Wed, Apr 11, 2018 at 01:45:05PM +0200, Tomasz Duszynski wrote:
> > This patchseries adds MRVL MVPP2 PMD to meson build system.
> >
> > Tomasz Duszynski (2):
> > net/mvpp2: rename the version file to standard
> > net/mvpp2: add meson build file
> >
>
> The patches look ok to me as far as the meson code is concerned, but I have
> no way to test compilation etc. It doesn't cause issues with other x86 or
> arm builds though, so:
>
> Series Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied to dpdk-next-build
/Bruce
next prev parent reply other threads:[~2018-04-13 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 11:45 Tomasz Duszynski
2018-04-11 11:45 ` [dpdk-dev] [PATCH 1/2] net/mvpp2: rename the version file to standard Tomasz Duszynski
2018-04-11 11:45 ` [dpdk-dev] [PATCH 2/2] net/mvpp2: add meson build file Tomasz Duszynski
2018-04-13 16:12 ` [dpdk-dev] [PATCH 0/2] add MRVL MVPP2 PMD to meson Bruce Richardson
2018-04-13 16:14 ` Bruce Richardson [this message]
2018-04-18 15:02 ` Bruce Richardson
2018-04-19 8:55 ` Tomasz Duszynski
2018-04-19 8:58 ` 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=20180413161428.GC37024@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dima@marvell.com \
--cc=jck@semihalf.com \
--cc=jianbo.liu@arm.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).