From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] kni: fix igb build with kernel 4.2
Date: Mon, 12 Oct 2015 12:51:24 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C83347F@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1440673919-17740-1-git-send-email-pablo.de.lara.guarch@intel.com>
> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Monday, October 12, 2015 1:50 PM
> To: De Lara Guarch, Pablo; dev@dpdk.org
> Subject: [dpdk-dev] kni: fix igb build with kernel 4.2
>
> From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
>
> Kernel 4.2 has introduced two new parameters in ndo_bridge_getlink,
> which breaks DPDK compilation.
>
> Linux: 7d4f8d87 ("switchdev: ad VLAN support for ports bridge-getlink")
>
> This patch adds the necessary checks to fix it.
>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
NACK this and previous patch. I was trying to send a v2 of this.
Sorry for the spam!
next prev parent reply other threads:[~2015-10-12 12:51 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] " 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 [this message]
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 ` [dpdk-dev] [PATCH v2 0/2] Fix " Ferruh Yigit
2015-11-04 1:36 ` 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=E115CCD9D858EF4F90C690B0DCB4D8973C83347F@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@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).