DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: David Marchand <david.marchand@redhat.com>, <dev@dpdk.org>,
	<stable@dpdk.org>, <daxuex.gao@intel.com>
Subject: [PATCH] kni: fix build on RHEL 9.1
Date: Fri, 6 Jan 2023 20:13:14 +0000	[thread overview]
Message-ID: <20230106201315.1179306-1-ferruh.yigit@amd.com> (raw)

Linux kernel in the RHEL9.1 seems backported Linux commit [1] that drops
netif_rx_ni().

This was fixed in DPDK [2] for vanilla Linux kernel.

Adding RHEL9.1 check for the netif_rx_ni() usage to fix build error.

[1]
2655926aea9b ("net: Remove netif_rx_any_context() and netif_rx_ni().")

[2]
Commit c98600d4bed6 ("kni: fix build with Linux 5.18")

Bugzilla ID: 1076
Cc: stable@dpdk.org

Signed-off-by: Ferruh Yigit <ferruh.yigit@amd.com>
---

Cc: daxuex.gao@intel.com
---
 kernel/linux/kni/compat.h | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/kernel/linux/kni/compat.h b/kernel/linux/kni/compat.h
index 3a86d12bbc5c..7aa6cd9fca75 100644
--- a/kernel/linux/kni/compat.h
+++ b/kernel/linux/kni/compat.h
@@ -146,6 +146,8 @@
 #define HAVE_ETH_HW_ADDR_SET
 #endif
 
-#if KERNEL_VERSION(5, 18, 0) > LINUX_VERSION_CODE
+#if KERNEL_VERSION(5, 18, 0) > LINUX_VERSION_CODE && \
+	(!(defined(RHEL_RELEASE_CODE) && \
+	 RHEL_RELEASE_VERSION(9, 1) <= RHEL_RELEASE_CODE))
 #define HAVE_NETIF_RX_NI
 #endif
-- 
2.25.1


             reply	other threads:[~2023-01-06 20:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06 20:13 Ferruh Yigit [this message]
2023-01-09  2:28 ` Gao, DaxueX
2023-01-09  9:07 ` David Marchand
2023-01-09 17:43   ` David Marchand

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=20230106201315.1179306-1-ferruh.yigit@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=david.marchand@redhat.com \
    --cc=daxuex.gao@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).