DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, <dev@dpdk.org>,
	David Marchand <david.marchand@redhat.com>,
	Daxue Gao <daxuex.gao@intel.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: Re: [PATCH dpdk-kmod] linux/igb_uio: fix build with kernel 5.18
Date: Fri, 16 Dec 2022 09:33:45 -0800	[thread overview]
Message-ID: <20221216093345.03b72dcb@hermes.local> (raw)
In-Reply-To: <20221216115732.3552650-1-ferruh.yigit@amd.com>

On Fri, 16 Dec 2022 11:57:32 +0000
Ferruh Yigit <ferruh.yigit@amd.com> wrote:

> In Linux kernel v5.18, "pci-dma-compat.h" wrapper file is removed [1].
> 
> Some APIs in that wrapper file were used by igb_uio kernel module and
> kernel module build fails after mentioned commit.
> 
> Fixed build for v5.18 by replacing APIs in igb_uio.
> 
> Replaced APIs are available in Linux v4.4 (minimum Linux kernel version
> supported by DPDK), so no Linux version check is needed.
> 

Makes sense, but lets put the correct versions in the commit description.
DPDK should not be trying to support unsupported kernel versions.

5.18 is End of Life now and so the one that matters is really 6.0.

Current DPDK 22 should be supporting last supported LTS which
in January will be 4.14

  reply	other threads:[~2022-12-16 17:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16 11:57 Ferruh Yigit
2022-12-16 17:33 ` Stephen Hemminger [this message]
2022-12-18 14:26   ` Ferruh Yigit
2022-12-22 15:35 ` Luca Boccassi
2023-02-05 17:41 ` Thomas Monjalon

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=20221216093345.03b72dcb@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=david.marchand@redhat.com \
    --cc=daxuex.gao@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --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).