DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1046] igb_uio fails to build with kernel 5.19
Date: Thu, 30 Jun 2022 18:05:41 +0000	[thread overview]
Message-ID: <bug-1046-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=1046

            Bug ID: 1046
           Summary: igb_uio fails to build with kernel 5.19
           Product: DPDK
           Version: 22.03
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: ferruhy@gmail.com
  Target Milestone: ---

$ make kernelversion
5.19.0-rc4


igb_uio:
repo: https://dpdk.org/git/dpdk-kmods
Commit e68a705cc5dc ("linux/igb_uio: fix build for switch fall through")


Build command:
make V=1 KSRC=<linux path>


Build error:
.../dpdk-kmods/linux/igb_uio/igb_uio.c: In function ‘igbuio_pci_probe’:
.../dpdk-kmods/linux/igb_uio/igb_uio.c:515:8:
    error: implicit declaration of function ‘pci_set_dma_mask’; did you mean
‘ipi_send_mask’? [-Werror=implicit-function-declaration]
  515 |  err = pci_set_dma_mask(dev,  DMA_BIT_MASK(64));
      |        ^~~~~~~~~~~~~~~~
.../dpdk-kmods/linux/igb_uio/igb_uio.c:521:8:
    error: implicit declaration of function ‘pci_set_consistent_dma_mask’
[-Werror=implicit-function-declaration]
  521 |  err = pci_set_consistent_dma_mask(dev, DMA_BIT_MASK(64));
      |        ^~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:249:
.../dpdk-kmods/linux/igb_uio/igb_uio.o] Error 1

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2022-06-30 18:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-1046-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /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).