From: Thomas Monjalon <thomas@monjalon.net>
To: Xiao Liang <xiliang@redhat.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [PATCH v2] kni:fix build failure as "ndo_change_mtu_rh74" not found in RHEL8
Date: Mon, 14 Jan 2019 14:03:14 +0100 [thread overview]
Message-ID: <10830259.vamm1FfuF6@xps> (raw)
In-Reply-To: <b14d672b-cb6b-8706-4219-85145f3ae442@intel.com>
19/12/2018 14:47, Ferruh Yigit:
> On 12/19/2018 7:07 AM, Xiao Liang wrote:
> > 'ndo_change_mtu_rh74' was changed to 'ndo_change_mtu' in RHEL8.
> >
> > Build error log:
> > /home/dpdk-18.11/kernel/linux/kni/compat.h:107:24: error: ‘const struct
> > net_device_ops’ has no member named ‘ndo_change_mtu_rh74’; did you mean
> > ‘ndo_change_mtu’?
> > #define ndo_change_mtu ndo_change_mtu_rh74
> >
> > ^~~~~~~~~~~~~~~~~~~
> > Signed-off-by: Xiao Liang <xiliang@redhat.com>
>
> Suggested title: 'kni: fix build on RHEL 8'
>
> And a request to backport:
> Cc: stable@dpdk.org
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied, thanks
prev parent reply other threads:[~2019-01-14 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 7:07 [PATCH v2] kni:fix build failure as "ndo_change_mtu_rh74" not found in RHEL8 Xiao Liang
2018-12-19 7:07 ` Xiao Liang
2018-12-19 13:26 ` Ferruh Yigit
2018-12-19 13:28 ` Ferruh Yigit
2018-12-19 13:47 ` Ferruh Yigit
2019-01-14 13:03 ` Thomas Monjalon [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=10830259.vamm1FfuF6@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=xiliang@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.