From: Thomas Monjalon <thomas@monjalon.net>
To: ferruh.yigit@intel.com, Yongseok Koh <yskoh@mellanox.com>,
ktraynor@redhat.com
Cc: stable@dpdk.org, michael.luo@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] kni: fix build on RHEL8
Date: Wed, 29 May 2019 23:48:07 +0200 [thread overview]
Message-ID: <1986574.YHl94pmo8i@xps> (raw)
In-Reply-To: <1558929727-56647-1-git-send-email-michael.luo@intel.com>
27/05/2019 06:02, michael.luo@intel.com:
> From: Luo Gaoliang <michael.luo@intel.com>
>
> Build error was seen on RHEL8 when CONFIG_RTE_KNI_KMOD_ETHTOOL is enabled.
>
> Build error log:
> /root/kni/dpdk-19.05/kernel/linux/kni/ethtool/igb/kcompat.h:3928:25:
> error: 'const struct net_device_ops' has no member named 'extended'
> #define ndo_set_vf_vlan extended.ndo_set_vf_vlan
> ^~~~~~~~
This module has been removed from DPDK:
http://git.dpdk.org/dpdk/commit/?id=ea6b39b5b84
Do we want to apply this patch directly in older releases (LTS)?
next prev parent reply other threads:[~2019-05-29 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 4:02 [dpdk-dev] " michael.luo
2019-05-29 21:48 ` Thomas Monjalon [this message]
2019-06-04 15:00 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2019-06-04 15:23 ` Kevin Traynor
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=1986574.YHl94pmo8i@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ktraynor@redhat.com \
--cc=michael.luo@intel.com \
--cc=stable@dpdk.org \
--cc=yskoh@mellanox.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).