DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olivier Matz <olivier.matz@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/4] misc compilation fixes
Date: Mon, 18 May 2015 10:17:57 +0200	[thread overview]
Message-ID: <1431937081-20083-1-git-send-email-olivier.matz@6wind.com> (raw)

This series contains compilation fixes.

Olivier Matz (4):
  examples/bond: fix compilation with clang
  examples/netmap: fix compilation for x86_x32-native-linuxapp-gcc
  pmds: fix 32 bits compilation with debug enabled
  examples/mk: add dependencies for timer and vm_power_manager

 examples/Makefile                          |   4 +-
 examples/bond/main.c                       |   2 +-
 examples/netmap_compat/lib/compat_netmap.c |   2 +-
 lib/librte_pmd_fm10k/fm10k_rxtx.c          |   5 +-
 lib/librte_pmd_i40e/i40e_ethdev.c          | 124 ++++++++++++++---------------
 lib/librte_pmd_i40e/i40e_rxtx.c            |   2 +-
 lib/librte_pmd_virtio/virtio_ethdev.c      |   2 +-
 7 files changed, 72 insertions(+), 69 deletions(-)

-- 
2.1.4

             reply	other threads:[~2015-05-18  8:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18  8:17 Olivier Matz [this message]
2015-05-18  8:17 ` [dpdk-dev] [PATCH 1/4] examples/bond: fix compilation with clang Olivier Matz
2015-05-18 13:53   ` Bruce Richardson
2015-05-18 13:57     ` Olivier MATZ
2015-05-18 14:00       ` Bruce Richardson
2015-05-18  8:17 ` [dpdk-dev] [PATCH 2/4] examples/netmap: fix compilation for x86_x32-native-linuxapp-gcc Olivier Matz
2015-05-18  8:18 ` [dpdk-dev] [PATCH 3/4] pmds: fix 32 bits compilation with debug enabled Olivier Matz
2015-05-18  8:18 ` [dpdk-dev] [PATCH 4/4] examples/mk: add dependencies for timer and vm_power_manager Olivier Matz
2015-05-19 15:47 ` [dpdk-dev] [PATCH 0/4] misc compilation fixes 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=1431937081-20083-1-git-send-email-olivier.matz@6wind.com \
    --to=olivier.matz@6wind.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).