From: "Jürgen Groß" <jgross@suse•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
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: Re: linux-next: build failure after merge of the xen-tip tree
Date: Thu, 12 Sep 2024 08:29:44 +0200 [thread overview]
Message-ID: <353d8403-1322-4c63-b1f5-cfc5b6c464f7@suse.com> (raw)
In-Reply-To: <20240912161333.1e65a06a@canb.auug.org.au>
[-- Attachment #1.1.1: Type: text/plain, Size: 457 bytes --]
On 12.09.24 08:13, Stephen Rothwell wrote:
> 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.
Now fixed.
Thanks,
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2024-09-12 6:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 6:13 linux-next: build failure after merge of the xen-tip tree Stephen Rothwell
2024-09-12 6:29 ` Jürgen Groß [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-04 14:27 Mark Brown
2026-03-04 14:37 ` Jürgen Groß
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=353d8403-1322-4c63-b1f5-cfc5b6c464f7@suse.com \
--to=jgross@suse$(echo .)com \
--cc=boris.ostrovsky@oracle$(echo .)com \
--cc=konrad.wilk@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sstabellini@kernel$(echo .)org \
--cc=xen-devel@lists$(echo .)xenproject.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