From: Mark Brown <broonie@kernel.org>
To: Val Packett <val@invisiblethingslab.com>,
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: Tue, 4 Aug 2026 17:28:36 +0100 [thread overview]
Message-ID: <anITNOG1qicdE-TI@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 310 bytes --]
Hi all,
After merging the xen-tip tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: modpost: "init_mm" [drivers/xen/xen-privcmd.ko] undefined!
Caused by commit
64d26fb2ad1f2 (xen: privcmd: fix ioeventfd crash under PV domain)
I have used the tree from next-20260803 instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-08-04 16:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 16:28 Mark Brown [this message]
2026-08-04 18:00 ` linux-next: build failure after merge of the xen-tip tree Val Packett
2026-08-05 5:33 ` Jürgen Groß
2026-08-05 7:18 ` Jürgen Groß
-- 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-12 6:13 Stephen Rothwell
2024-09-12 6:29 ` 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=anITNOG1qicdE-TI@sirena.org.uk \
--to=broonie@kernel.org \
--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=val@invisiblethingslab.com \
--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