From: Mohammed Gamal <mgamal@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] kni: Fix build on RHEL 8
Date: Tue, 27 Nov 2018 12:13:22 +0100 [thread overview]
Message-ID: <1543317202.5400.13.camel@redhat.com> (raw)
In-Reply-To: <26d50d0f-8eb0-608f-9aed-5f3b39a85ff8@intel.com>
On Tue, 2018-11-27 at 10:55 +0000, Ferruh Yigit wrote:
> On 11/26/2018 8:45 PM, Mohammed Gamal wrote:
> > As RHEL8 beta has been released and is based on recent upstream
> > kernels
> > which don't use ndo_change_mtu_rh74 function. Fix the build so that
> > it
> > doesn't fail because the function is missing
> >
> > Signed-off-by: Mohammed Gamal <mgamal@redhat.com>
> > ---
> > kernel/linux/kni/compat.h | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/kernel/linux/kni/compat.h b/kernel/linux/kni/compat.h
> > index 5aadebb..bc81d0c 100644
> > --- a/kernel/linux/kni/compat.h
> > +++ b/kernel/linux/kni/compat.h
> > @@ -103,7 +103,8 @@
> > #endif
> >
> > #if (defined(RHEL_RELEASE_CODE) && \
> > - (RHEL_RELEASE_CODE >= RHEL_RELEASE_VERSION(7, 5)))
> > + (RHEL_RELEASE_CODE >= RHEL_RELEASE_VERSION(7, 5)) && \
> > + (RHEL_RELEASE_CODE < RHEL_RELEASE_VERSION(8, 0)))
> > #define ndo_change_mtu ndo_change_mtu_rh74
>
> What RHEL use, can you please confirm it turns back to
> `ndo_change_mtu`, instead
> of something like `ndo_change_mtu_rh8x`?
There are no such functions in the RHEL8 kernel. You may check the
kernel source code from the SRPM available here:
http://ftp.redhat.com/redhat/rhel/rhel-8-beta/baseos/source/Packages/ke
rnel-4.18.0-32.el8.src.rpm
>
> > #endif
> >
> >
>
>
next prev parent reply other threads:[~2018-11-27 11:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 20:45 Mohammed Gamal
2018-11-27 10:55 ` Ferruh Yigit
2018-11-27 11:13 ` Mohammed Gamal [this message]
2018-11-27 13:38 ` Ferruh Yigit
2018-12-19 13:27 ` Ferruh Yigit
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=1543317202.5400.13.camel@redhat.com \
--to=mgamal@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).