From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Joerg Roedel <joro@8bytes.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the iommu tree
Date: Tue, 8 Jun 2021 13:56:41 +1000 [thread overview]
Message-ID: <20210608135641.67e123e6@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
Hi all,
After merging the iommu tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
WARNING: modpost: vmlinux.o(.text.unlikely+0xddf06): Section mismatch in reference from the function detect_ivrs() to the variable .init.data:amd_iommu_force_enable
The function detect_ivrs() references
the variable __initdata amd_iommu_force_enable.
This is often because detect_ivrs lacks a __initdata
annotation or the annotation of amd_iommu_force_enable is wrong.
Introduced by commit
b1e650db2cc4 ("iommu/amd: Add amd_iommu=force_enable option")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-06-08 3:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 3:56 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-16 10:42 linux-next: build warning after merge of the iommu tree Stephen Rothwell
2025-07-17 10:04 ` Will Deacon
2024-07-09 9:06 Stephen Rothwell
2024-07-09 10:08 ` Will Deacon
2019-02-27 2:20 Stephen Rothwell
2019-02-27 18:48 ` sathyanarayanan kuppuswamy
2018-11-08 1:39 Stephen Rothwell
2018-11-08 9:30 ` Joerg Roedel
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=20210608135641.67e123e6@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).