From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/2] igb_uio: fix compability on old kernel
Date: Fri, 01 Aug 2014 15:10:34 +0200 [thread overview]
Message-ID: <9317787.qKVt3oyQbN@xps13> (raw)
In-Reply-To: <20140725103627.4ca989b7@haswell.linuxnetplumber.net>
2014-07-25 10:36, Stephen Hemminger:
> Add more compatibility wrappers, and split out all the wrapper
> code to a separate file. Builds on Debian Squeeze (2.6.32) which
> is oldest version of kernel current DPDK supports.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
Applied for version 1.7.1.
There are still some compilation issues with RHEL:
include/linux/pci.h:1572: note: previous declaration of ‘pci_num_vf’ was here
include/linux/pci.h:868: note: previous declaration of ‘pci_intx_mask_supported’ was here
include/linux/pci.h:869: note: previous declaration of ‘pci_check_and_mask_intx’ was here
Some ifdefs are missing but I don't want to dig into RHEL kernel headers to
find what is the first RHEL release to support these functions.
By the way, if someone knows an easy method to get all RHEL kernel headers
or to know the release where a symbol appeared, it would be very useful.
--
Thomas
next prev parent reply other threads:[~2014-08-01 13:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 17:36 Stephen Hemminger
2014-07-25 17:37 ` [dpdk-dev] [PATCH 2/2] igb_uio: handle no IRQ fallback Stephen Hemminger
2014-08-01 13:11 ` Thomas Monjalon
2014-08-01 13:10 ` Thomas Monjalon [this message]
2014-08-22 17:29 ` [dpdk-dev] [PATCH 1/2] igb_uio: fix compability on old kernel Sanford, Robert
2014-08-22 18:09 ` Robert Sanford
2014-08-23 15:14 ` Stephen Hemminger
2014-08-26 16:08 ` Sanford, Robert
2014-09-01 11:15 ` Thomas Monjalon
2014-09-01 15:07 ` Guillaume Gaudonville
2014-09-01 14:55 ` Guillaume Gaudonville
2014-09-03 2:28 ` 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=9317787.qKVt3oyQbN@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).