DPDK patches and discussions
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.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: Thu, 22 Dec 2022 15:35:48 +0000	[thread overview]
Message-ID: <CAMw=ZnSC3o+5oZrh4TcUt1JK93LQxeJ_DzxA44zTXkzfmLmN_w@mail.gmail.com> (raw)
In-Reply-To: <20221216115732.3552650-1-ferruh.yigit@amd.com>

On Fri, 16 Dec 2022 at 12:57, 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.
>
> [1]
> Commit 7968778914e5 ("PCI: Remove the deprecated "pci-dma-compat.h" API")
>
> Bugzilla ID: 1142
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@amd.com>
> ---
> Cc: Daxue Gao <daxuex.gao@intel.com>
>
> Cc: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> This also needs to be backported to v19.11 LTS
> ---
>  linux/igb_uio/igb_uio.c | 8 +-------
>  1 file changed, 1 insertion(+), 7 deletions(-)

Tested-by: Luca Boccassi <bluca@debian.org>

  parent reply	other threads:[~2022-12-22 15:36 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
2022-12-18 14:26   ` Ferruh Yigit
2022-12-22 15:35 ` Luca Boccassi [this message]
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='CAMw=ZnSC3o+5oZrh4TcUt1JK93LQxeJ_DzxA44zTXkzfmLmN_w@mail.gmail.com' \
    --to=bluca@debian.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).