From: Bruce Richardson <bruce.richardson@intel.com>
To: Luca Boccassi <bluca@debian.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/7] update dpdk-next-build to 17.11-rc1
Date: Tue, 17 Oct 2017 14:14:42 +0100 [thread overview]
Message-ID: <20171017131442.GB10584@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <20171017131147.GA10584@bricha3-MOBL3.ger.corp.intel.com>
On Tue, Oct 17, 2017 at 02:11:47PM +0100, Bruce Richardson wrote:
> On Tue, Oct 17, 2017 at 12:58:32PM +0100, Luca Boccassi wrote:
> > On Tue, 2017-10-17 at 11:41 +0100, Bruce Richardson wrote:
> > > With the large number of changes in 17.11-rc1, the dpdk-next-build
> > > patches would no longer apply and compile cleanly on top of the main
> > > tree. To allow next-build to be rebased on top of master, the changes
> > > listed below needed to be made to the code.
> > >
> > > NOTE: appart from the last patch which may be kept separate as it's
> > > not a compilation fix, these patches will be merged into existing
> > > commits in next-build so as to ensure a clear history on top of
> > > master.
> > >
> > > Bruce Richardson (7):
> > > build: add rte_bitmap.h to eal
> > > build: remove rte_bitmap.h from rte_sched lib
> > > build: add gso library
> > > eal: add additional memcpy and cycles C files to build
> > > efd: add new avx2 standalone file to build
> > > app/test-pmd: add dependency on new gso library
> > > eal/x86: compile memcpy for dynamic dispatch
> > >
> > > app/test-pmd/meson.build | 2 +-
> > > lib/librte_eal/common/arch/x86/meson.build | 28
> > > +++++++++++++++++++++++-
> > > lib/librte_eal/common/include/meson.build | 1 +
> > > lib/librte_eal/linuxapp/eal/meson.build | 1 +
> > > lib/librte_efd/meson.build | 19 ++++++++++++++++
> > > lib/librte_gso/meson.build | 35
> > > ++++++++++++++++++++++++++++++
> > > lib/librte_sched/meson.build | 2 +-
> > > lib/meson.build | 2 +-
> > > 8 files changed, 86 insertions(+), 4 deletions(-)
> > > create mode 100644 lib/librte_gso/meson.build
> >
> > Reviewed-by: Luca Boccassi <bluca@debian.org>
> >
> > LGTM, thanks!
> >
> > --
> > Kind regards,
> > Luca Boccassi
>
> Patches merged to relevant commits in dpdk-next-build
... along with a version number update in the top-level meson.build file
>
> /Bruce
prev parent reply other threads:[~2017-10-17 13:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 10:41 Bruce Richardson
2017-10-17 10:41 ` [dpdk-dev] [PATCH 1/7] build: add rte_bitmap.h to eal Bruce Richardson
2017-10-17 10:41 ` [dpdk-dev] [PATCH 2/7] build: remove rte_bitmap.h from rte_sched lib Bruce Richardson
2017-10-17 10:41 ` [dpdk-dev] [PATCH 3/7] build: add gso library Bruce Richardson
2017-10-17 10:41 ` [dpdk-dev] [PATCH 4/7] eal/x86: add additional memcpy and cycles C files to build Bruce Richardson
2017-10-17 10:41 ` [dpdk-dev] [PATCH 5/7] efd: add new avx2 standalone file " Bruce Richardson
2017-10-17 10:41 ` [dpdk-dev] [PATCH 6/7] app/test-pmd: add dependency on new gso library Bruce Richardson
2017-10-17 10:41 ` [dpdk-dev] [PATCH 7/7] eal/x86: compile memcpy for dynamic dispatch Bruce Richardson
2017-10-17 11:58 ` [dpdk-dev] [PATCH 0/7] update dpdk-next-build to 17.11-rc1 Luca Boccassi
2017-10-17 13:11 ` Bruce Richardson
2017-10-17 13:14 ` Bruce Richardson [this message]
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=20171017131442.GB10584@bricha3-MOBL3.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
/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).