From: Kevin Traynor <ktraynor@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Yongseok Koh <yskoh@mellanox.com>
Cc: stable@dpdk.org, michael.luo@intel.com, dev@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] kni: fix build on RHEL8
Date: Tue, 4 Jun 2019 16:23:37 +0100 [thread overview]
Message-ID: <5925cca9-be86-7369-cb4b-407635cf76e5@redhat.com> (raw)
In-Reply-To: <2e6a3472-03d8-bc4f-6345-e02faca89645@intel.com>
On 04/06/2019 16:00, Ferruh Yigit wrote:
> On 5/29/2019 10:48 PM, Thomas Monjalon wrote:
>> 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)?
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> stable mail list already in the cc, but
>
> Kevin, Yongsek,
> This patch won't be in the master repo, is there anything needs to be done to
> include the patch in LTS, or is this mail sufficient?
>
Hi Ferruh, this mail is enough, will note it.
thanks,
Kevin.
> Thanks,
> ferruh
>
prev parent reply other threads:[~2019-06-04 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 4:02 michael.luo
2019-05-29 21:48 ` Thomas Monjalon
2019-06-04 15:00 ` Ferruh Yigit
2019-06-04 15:23 ` Kevin Traynor [this message]
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=5925cca9-be86-7369-cb4b-407635cf76e5@redhat.com \
--to=ktraynor@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=michael.luo@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--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).