public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jason Gunthorpe <jgg@nvidia•com>
Cc: Jason Gunthorpe <jgg@ziepe•ca>, Yi Liu <yi.l.liu@intel•com>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the iommufd tree
Date: Thu, 30 Mar 2023 12:54:08 +1100	[thread overview]
Message-ID: <20230330125408.42b444a0@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]

Hi all,

After merging the iommufd tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/iommu/iommufd/hw_pagetable.c: In function 'iommufd_hwpt_alloc':
drivers/iommu/iommufd/hw_pagetable.c:135:33: error: passing argument 1 of 'iommufd_get_ioas' from incompatible pointer type [-Werror=incompatible-pointer-types]
  135 |         ioas = iommufd_get_ioas(ucmd, cmd->pt_id);
      |                                 ^~~~
      |                                 |
      |                                 struct iommufd_ucmd *
In file included from drivers/iommu/iommufd/hw_pagetable.c:8:
drivers/iommu/iommufd/iommufd_private.h:216:73: note: expected 'struct iommufd_ctx *' but argument is of type 'struct iommufd_ucmd *'
  216 | static inline struct iommufd_ioas *iommufd_get_ioas(struct iommufd_ctx *ictx,
      |                                                     ~~~~~~~~~~~~~~~~~~~~^~~~

Caused by commit

  a7358b11764e ("iommu/iommufd: Pass iommufd_ctx pointer in iommufd_get_ioas()")

interacting with commit

  8295188cc9e6 ("iommufd: Add IOMMU_HWPT_ALLOC")

it should have been fixed up in the merge commit

  085121c1d1bb ("Merge branch 'ko-iommufd/wip/for-nesting' into k.o-iommufd/for-next")

I have used the iommufd tree from next-20230329 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-03-30  1:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30  1:54 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-15 11:04 linux-next: build failure after merge of the iommufd tree Stephen Rothwell
2023-08-15 11:34 ` Jason Gunthorpe
2024-07-12  5:58 Stephen Rothwell
2024-07-12 12:05 ` Jason Gunthorpe

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=20230330125408.42b444a0@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=jgg@nvidia$(echo .)com \
    --cc=jgg@ziepe$(echo .)ca \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=yi.l.liu@intel$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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