From: Bruce Richardson <bruce.richardson@intel.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org, ferruh.yigit@intel.com, hemant.agrawal@nxp.com
Subject: [dpdk-dev] Pull request for dpdk-next-build
Date: Thu, 15 Mar 2018 17:19:43 +0000 [thread overview]
Message-ID: <20180315171943.GA4776@bricha3-MOBL.ger.corp.intel.com> (raw)
The following changes since commit c06ddf9698e0c2a9653cfa971f9ddc205065662c:
meter: add configuration profile (2018-02-19 22:28:05 +0100)
are available in the Git repository at:
http://dpdk.org/git/draft/dpdk-next-build
for you to fetch changes up to a4ffb69205a55ed6acae00b324165aecbbc67dfb:
build: add meson cross compile config for dpaaX (2018-03-15 17:01:01 +0000)
----------------------------------------------------------------
Bruce Richardson (6):
examples: fix building examples with meson
app: generalize building of apps using meson
app/proc_info: rename folder to remove underscore
app: add all remaining apps to meson build
net/virtio: add driver to meson build
net/pcap: simplify dependency checking using meson
Hemant Agrawal (10):
event/dpaa: fix include header
bus/dpaa: fix the BE compilation issue
dpaa: prepare for 32 bit compilation
dpaa2: prepare for 32 bit compilation
bus/fslmc: add 32 bit functional support for ARM
bus/dpaa: enabling dpaa compilation for other platforms
bus/fslmc: enabling dpaa2 compilation for other platforms
config: add dpaaX build support in common linuxapp
build: add meson support for dpaaX platforms
build: add meson cross compile config for dpaaX
app/Makefile | 2 +-
app/meson.build | 56 ++++++++++++++-
app/pdump/meson.build | 6 ++
app/{proc_info => proc-info}/Makefile | 0
app/{proc_info => proc-info}/main.c | 0
app/proc-info/meson.build | 6 ++
app/test-bbdev/meson.build | 9 +++
app/test-crypto-perf/meson.build | 14 ++++
app/test-eventdev/meson.build | 18 +----
app/test-pmd/meson.build | 23 ++-----
config/arm/arm64_dpaa2_linuxapp_gcc | 15 +++++
config/arm/arm64_dpaa_linuxapp_gcc | 15 +++++
config/arm/meson.build | 13 ++++
config/common_armv8a_linuxapp | 58 ----------------
config/common_base | 4 ++
config/common_linuxapp | 14 ++++
config/rte_config.h | 12 +++-
drivers/bus/dpaa/base/fman/fman.c | 2 +-
drivers/bus/dpaa/base/qbman/bman_driver.c | 2 +-
drivers/bus/dpaa/base/qbman/qman.c | 5 +-
drivers/bus/dpaa/base/qbman/qman_driver.c | 5 +-
drivers/bus/dpaa/dpaa_bus.c | 3 +-
drivers/bus/dpaa/include/compat.h | 30 ++++++++-
drivers/bus/dpaa/meson.build | 29 ++++++++
drivers/bus/fslmc/fslmc_vfio.c | 10 +--
drivers/bus/fslmc/mc/fsl_mc_cmd.h | 2 +-
drivers/bus/fslmc/meson.build | 27 ++++++++
drivers/bus/fslmc/portal/dpaa2_hw_dpio.c | 22 +++---
drivers/bus/fslmc/portal/dpaa2_hw_pvt.h | 37 +++++-----
drivers/bus/fslmc/qbman/qbman_portal.c | 14 ++--
drivers/bus/fslmc/qbman/qbman_sys.h | 30 ++++++++-
drivers/bus/fslmc/qbman/qbman_sys_decl.h | 23 +++++++
drivers/bus/meson.build | 2 +-
drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c | 101 ++++++++++++++--------------
drivers/crypto/dpaa2_sec/meson.build | 14 ++++
drivers/crypto/dpaa_sec/dpaa_sec.c | 30 ++++-----
drivers/crypto/dpaa_sec/meson.build | 13 ++++
drivers/crypto/meson.build | 4 +-
drivers/event/dpaa/dpaa_eventdev.c | 2 +-
drivers/event/dpaa/meson.build | 10 +++
drivers/event/dpaa2/dpaa2_eventdev.c | 10 +--
drivers/event/dpaa2/meson.build | 11 +++
drivers/event/meson.build | 2 +-
drivers/mempool/dpaa/dpaa_mempool.c | 10 +--
drivers/mempool/dpaa/dpaa_mempool.h | 2 +-
drivers/mempool/dpaa/meson.build | 9 +++
drivers/mempool/dpaa2/dpaa2_hw_mempool.c | 8 +--
drivers/mempool/dpaa2/meson.build | 9 +++
drivers/mempool/meson.build | 2 +-
drivers/net/dpaa/dpaa_rxtx.c | 19 +++---
drivers/net/dpaa/meson.build | 14 ++++
drivers/net/dpaa2/Makefile | 1 -
drivers/net/dpaa2/base/dpaa2_hw_dpni.c | 2 +-
drivers/net/dpaa2/dpaa2_ethdev.c | 6 +-
drivers/net/dpaa2/dpaa2_rxtx.c | 63 +++++++++--------
drivers/net/dpaa2/meson.build | 15 +++++
drivers/net/meson.build | 4 +-
drivers/net/pcap/meson.build | 20 ++----
drivers/net/virtio/meson.build | 27 ++++++++
examples/ip_pipeline/meson.build | 1 +
examples/qos_meter/meson.build | 1 +
61 files changed, 616 insertions(+), 302 deletions(-)
create mode 100644 app/pdump/meson.build
rename app/{proc_info => proc-info}/Makefile (100%)
rename app/{proc_info => proc-info}/main.c (100%)
create mode 100644 app/proc-info/meson.build
create mode 100644 app/test-bbdev/meson.build
create mode 100644 app/test-crypto-perf/meson.build
create mode 100644 config/arm/arm64_dpaa2_linuxapp_gcc
create mode 100644 config/arm/arm64_dpaa_linuxapp_gcc
create mode 100644 drivers/bus/dpaa/meson.build
create mode 100644 drivers/bus/fslmc/meson.build
create mode 100644 drivers/crypto/dpaa2_sec/meson.build
create mode 100644 drivers/crypto/dpaa_sec/meson.build
create mode 100644 drivers/event/dpaa/meson.build
create mode 100644 drivers/event/dpaa2/meson.build
create mode 100644 drivers/mempool/dpaa/meson.build
create mode 100644 drivers/mempool/dpaa2/meson.build
create mode 100644 drivers/net/dpaa/meson.build
create mode 100644 drivers/net/dpaa2/meson.build
create mode 100644 drivers/net/virtio/meson.build
next reply other threads:[~2018-03-15 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 17:19 Bruce Richardson [this message]
2018-03-20 22:39 ` Thomas Monjalon
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=20180315171943.GA4776@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=thomas@monjalon.net \
/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).