From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Juergen Gross <jgross@suse.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Xen Devel <xen-devel@lists.xenproject.org>
Cc: 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 xen-tip tree
Date: Thu, 12 Sep 2024 16:13:33 +1000 [thread overview]
Message-ID: <20240912161333.1e65a06a@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 498 bytes --]
Hi all,
After merging the xen-tip tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: modpost: "acpi_os_ioremap" [drivers/gpu/drm/gma500/gma500_gfx.ko] undefined!
Caused by commit
de4237fd5174 ("xen: allow mapping ACPI data using a different physical address")
acpi_os_ioremap is not exported to modules.
I have used the xen-tip tree from next-20240910 (as the next-20240911
version had a different build failure).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-09-12 6:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 6:13 Stephen Rothwell [this message]
2024-09-12 6:29 ` linux-next: build failure after merge of the xen-tip tree Jürgen Groß
-- strict thread matches above, loose matches on Subject: below --
2024-09-11 6:04 Stephen Rothwell
2021-09-15 1:11 Stephen Rothwell
2018-07-30 5:12 Stephen Rothwell
2018-07-30 7:40 ` Oleksandr Andrushchenko
2018-08-16 0:09 ` Stephen Rothwell
2017-08-31 5:22 Stephen Rothwell
2015-04-13 8:09 Stephen Rothwell
2015-04-13 8:36 ` Bob Liu
2015-04-15 5:00 ` Stephen Rothwell
2015-04-15 10:03 ` David Vrabel
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=20240912161333.1e65a06a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).