From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jason Gunthorpe <jgg@nvidia•com>
Cc: Jason Gunthorpe <jgg@ziepe•ca>,
Lu Baolu <baolu.lu@linux•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: Fri, 12 Jul 2024 15:58:42 +1000 [thread overview]
Message-ID: <20240712155842.240a85e3@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2125 bytes --]
Hi all,
After merging the iommufd tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from include/linux/container_of.h:5,
from include/linux/list.h:5,
from include/linux/wait.h:7,
from include/linux/wait_bit.h:8,
from include/linux/fs.h:6,
from drivers/iommu/iommufd/fault.c:7:
drivers/iommu/iommufd/fault.c: In function 'iommufd_fault_fops_write':
drivers/iommu/iommufd/fault.c:308:57: error: comparison between 'enum iommufd_page_response_code' and 'enum iommu_page_response_code' [-Werror=enum-compare]
308 | static_assert(IOMMUFD_PAGE_RESP_SUCCESS ==
| ^~
include/linux/build_bug.h:78:56: note: in definition of macro '__static_assert'
78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
| ^~~~
drivers/iommu/iommufd/fault.c:308:17: note: in expansion of macro 'static_assert'
308 | static_assert(IOMMUFD_PAGE_RESP_SUCCESS ==
| ^~~~~~~~~~~~~
drivers/iommu/iommufd/fault.c:310:57: error: comparison between 'enum iommufd_page_response_code' and 'enum iommu_page_response_code' [-Werror=enum-compare]
310 | static_assert(IOMMUFD_PAGE_RESP_INVALID ==
| ^~
include/linux/build_bug.h:78:56: note: in definition of macro '__static_assert'
78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
| ^~~~
drivers/iommu/iommufd/fault.c:310:17: note: in expansion of macro 'static_assert'
310 | static_assert(IOMMUFD_PAGE_RESP_INVALID ==
| ^~~~~~~~~~~~~
cc1: all warnings being treated as errors
Caused by commit
c7a0991733cc ("iommufd: Add check on user response code")
I have used the iommufd tree from next-20240711 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-07-12 5:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 5:58 Stephen Rothwell [this message]
2024-07-12 12:05 ` linux-next: build failure after merge of the iommufd tree Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2023-08-15 11:04 Stephen Rothwell
2023-08-15 11:34 ` Jason Gunthorpe
2023-03-30 1:54 Stephen Rothwell
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=20240712155842.240a85e3@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=baolu.lu@linux$(echo .)intel.com \
--cc=jgg@nvidia$(echo .)com \
--cc=jgg@ziepe$(echo .)ca \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/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