DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] kni: fix compilation issue on kernel 4.0.0
Date: Wed, 29 Apr 2015 15:05:26 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D89727298A32@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <4644867.VTdQjDrnCJ@xps13>

Hi Thomas,

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Wednesday, April 29, 2015 2:20 PM
> To: De Lara Guarch, Pablo
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] kni: fix compilation issue on kernel 4.0.0
> 
> 2015-04-28 18:37, Pablo de Lara:
> > Due to API changes in function pointer ndo_bridge_setlink
> > (commit ad41faa8) and the rename of functions vlan_tx_*
> > (commit df8a39de) in kernel 4.0, DPDK would not build.
> >
> > This patch adds the properly checks to fix the compilation.
> >
> > Reported-by: Stephen Hemminger <stephen@networkplumber.org>
> > Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> 
> Pablo, I have another error with Linux 3.19 when KNI vhost is enabled:
> 
> lib/librte_eal/linuxapp/kni/kni_vhost.c:365:35: error:
> ‘struct msghdr’ has no member named ‘msg_iov’

Thanks for reporting, I didn't see that. I will send a patch for that as soon as I can.

Pablo


  reply	other threads:[~2015-04-29 15:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 17:37 Pablo de Lara
2015-04-29 13:19 ` Thomas Monjalon
2015-04-29 15:05   ` De Lara Guarch, Pablo [this message]
2015-05-11  9:07 ` 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=E115CCD9D858EF4F90C690B0DCB4D89727298A32@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.com \
    /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).