From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 0/2] Fix build with kernel 4.2
Date: Mon, 12 Oct 2015 14:25:33 +0100 [thread overview]
Message-ID: <20151012132533.GA22446@sivlogin002.ir.intel.com> (raw)
In-Reply-To: <1444654378-19212-1-git-send-email-pablo.de.lara.guarch@intel.com>
On Mon, Oct 12, 2015 at 01:52:56PM +0100, Pablo de Lara wrote:
> Kernel 4.2 has introduced two new parameters in
> function ndo_bridge_netlink and therefore,
> DPDK does not build with it.
>
> This patchset adds the necessary checks and
> rename a previous defined macro, in order
> to have a more meaningful name.
>
> Changes in v2:
> - Split patch in two patches
>
> Pablo de Lara (2):
> kni: rename HAVE_NDO_BRIDGE_GETLINK_FILTER_MASK macro
> kni: fix igb build with kernel 4.2
>
> lib/librte_eal/linuxapp/kni/ethtool/igb/igb_main.c | 13 +++++++++----
> lib/librte_eal/linuxapp/kni/ethtool/igb/kcompat.h | 7 ++++++-
> 2 files changed, 15 insertions(+), 5 deletions(-)
>
> --
> 2.1.0
>
Series Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2015-10-12 13:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1444654017-18819-1-git-send-email-pablo.de.lara.guarch@intel.com>
2015-08-27 11:11 ` [dpdk-dev] [PATCH] kni: fix igb " Pablo de Lara
2015-10-12 12:46 ` [dpdk-dev] " Pablo de Lara
2015-10-12 12:49 ` Pablo de Lara
2015-10-12 12:51 ` De Lara Guarch, Pablo
2015-10-12 12:52 ` [dpdk-dev] [PATCH v2 0/2] Fix " Pablo de Lara
2015-10-12 12:52 ` [dpdk-dev] [PATCH v2 1/2] kni: rename HAVE_NDO_BRIDGE_GETLINK_FILTER_MASK macro Pablo de Lara
2015-10-12 12:52 ` [dpdk-dev] [PATCH v2 2/2] kni: fix igb build with kernel 4.2 Pablo de Lara
2015-10-12 13:25 ` Ferruh Yigit [this message]
2015-11-04 1:36 ` [dpdk-dev] [PATCH v2 0/2] Fix " 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=20151012132533.GA22446@sivlogin002.ir.intel.com \
--to=ferruh.yigit@intel.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).