From: Jerry Hao OS <jerryhao@os.amperecomputing.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Jerry Hao OS <jerryhao@os.amperecomputing.com>
Subject: [dpdk-dev] [PATCH 0/1] build: add emag(arm64) platform and default config
Date: Thu, 12 Sep 2019 08:52:34 +0000 [thread overview]
Message-ID: <20190912085119.27171-1-jerryhao@os.amperecomputing.com> (raw)
*** BLURB HERE ***
Jerry Hao OS (1):
build: add emag(arm64) platform and default config
config/arm/arm64_emag_linux_gcc | 15 ++++++++++++
config/arm/meson.build | 11 ++++++++-
config/defconfig_arm64-emag-linux-gcc | 1 +
config/defconfig_arm64-emag-linuxapp-gcc | 11 +++++++++
mk/machine/emag/rte.vars.mk | 31 ++++++++++++++++++++++++
5 files changed, 68 insertions(+), 1 deletion(-)
create mode 100644 config/arm/arm64_emag_linux_gcc
create mode 120000 config/defconfig_arm64-emag-linux-gcc
create mode 100644 config/defconfig_arm64-emag-linuxapp-gcc
create mode 100644 mk/machine/emag/rte.vars.mk
--
2.17.1
next reply other threads:[~2019-09-12 8:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 8:52 Jerry Hao OS [this message]
2019-09-12 8:52 ` [dpdk-dev] [PATCH 1/1] build: add emag(arm64) platform and default config Jerry Hao OS
2019-09-12 9:31 ` Gavin Hu (Arm Technology China)
2019-09-12 16:25 ` Jerin Jacob
2019-09-16 3:43 ` [dpdk-dev] [PATCH v2] " Jerry Hao OS
2019-10-09 2:44 ` [dpdk-dev] [PATCH v3] " Gavin Hu
2019-10-11 11:45 ` Jerin Jacob
2019-10-14 9:34 ` [dpdk-dev] [PATCH v4] build: add emag target Gavin Hu
2019-11-20 23:22 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2019-09-12 4:51 [dpdk-dev] [PATCH 0/1] build: add emag(arm64) platform and default config Jerry Hao OS
2019-09-12 2:44 Jerry Hao OS
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=20190912085119.27171-1-jerryhao@os.amperecomputing.com \
--to=jerryhao@os.amperecomputing.com \
--cc=dev@dpdk.org \
--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).