From: Jason Gunthorpe <jgg@nvidia.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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: Re: linux-next: build failure after merge of the iommufd tree
Date: Fri, 12 Jul 2024 09:05:58 -0300 [thread overview]
Message-ID: <20240712120558.GO1482543@nvidia.com> (raw)
In-Reply-To: <20240712155842.240a85e3@canb.auug.org.au>
On Fri, Jul 12, 2024 at 03:58:42PM +1000, Stephen Rothwell wrote:
> 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 ==
> | ^~
Oh my compiler didn't complain, I added some casts
Thanks,
Jason
next prev parent reply other threads:[~2024-07-12 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 5:58 linux-next: build failure after merge of the iommufd tree Stephen Rothwell
2024-07-12 12:05 ` Jason Gunthorpe [this message]
-- 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=20240712120558.GO1482543@nvidia.com \
--to=jgg@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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