From: Jason Gunthorpe <jgg@nvidia.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the iommufd tree
Date: Fri, 21 Mar 2025 08:39:32 -0300 [thread overview]
Message-ID: <20250321113932.GU206770@nvidia.com> (raw)
In-Reply-To: <20250321193600.2bfe03bb@canb.auug.org.au>
On Fri, Mar 21, 2025 at 07:36:00PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the iommufd tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> vmlinux.o: warning: objtool: iommu_dma_get_msi_page() falls through to next function __iommu_dma_unmap()
>
> I have no idea where that came from.
Me too, I've been ignoring weird objtool things because I don't know
what to do with them :\
Jason
next prev parent reply other threads:[~2025-03-21 11:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 8:36 linux-next: build warning after merge of the iommufd tree Stephen Rothwell
2025-03-21 11:39 ` Jason Gunthorpe [this message]
2025-03-26 2:43 ` Valdis Klētnieks
-- strict thread matches above, loose matches on Subject: below --
2025-07-11 8:35 Stephen Rothwell
2025-07-11 14:04 ` Jason Gunthorpe
2025-07-11 8:25 Stephen Rothwell
2025-07-11 13:38 ` Jason Gunthorpe
2025-03-18 10:33 Stephen Rothwell
2025-03-28 6:57 ` Stephen Rothwell
2025-03-28 11:49 ` Bagas Sanjaya
2023-03-31 4:41 Stephen Rothwell
2023-03-31 17:45 ` Jason Gunthorpe
2023-03-31 4:31 Stephen Rothwell
2023-03-31 5:09 ` Nicolin Chen
2023-03-31 17:44 ` Jason Gunthorpe
2022-11-08 5:51 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=20250321113932.GU206770@nvidia.com \
--to=jgg@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.