From: Andy Green <andy@warmcat.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] dpdk header fixes for aarch64
Date: Mon, 28 May 2018 10:29:00 +0800 [thread overview]
Message-ID: <152747443129.35192.15673273827095899997.stgit@localhost.localdomain> (raw)
On Xenial / 16.04 native aarch64 build with gcc 5.4.0,
lagopus build finds a couple more issues hiding in
dpdk headers.
---
Andy Green (2):
ring: fix declaration after code
ring: fix sign conversion warning
lib/librte_ring/rte_ring.h | 2 +-
lib/librte_ring/rte_ring_c11_mem.h | 8 ++++++--
2 files changed, 7 insertions(+), 3 deletions(-)
--
Signature
next reply other threads:[~2018-05-28 2:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 2:29 Andy Green [this message]
2018-05-28 2:29 ` [dpdk-dev] [PATCH 1/2] ring: fix declaration after code Andy Green
2018-05-28 8:15 ` Gavin Hu
2018-05-28 8:46 ` Andy Green
2018-05-28 8:54 ` Gavin Hu
2018-05-28 2:29 ` [dpdk-dev] [PATCH 2/2] ring: fix sign conversion warning Andy Green
2018-05-28 9:03 ` [dpdk-dev] [PATCH v2 0/2] dpdk header fixes for aarch64 Andy Green
2018-05-28 9:03 ` [dpdk-dev] [PATCH v2 1/2] ring: fix declaration after code Andy Green
2018-07-16 7:15 ` Olivier Matz
2018-05-28 9:03 ` [dpdk-dev] [PATCH v2 2/2] ring: fix sign conversion warning Andy Green
2018-07-16 7:16 ` Olivier Matz
2018-07-26 13:30 ` [dpdk-dev] [PATCH v2 0/2] dpdk header fixes for aarch64 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=152747443129.35192.15673273827095899997.stgit@localhost.localdomain \
--to=andy@warmcat.com \
--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).