From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Mark Brown <broonie@kernel.org>,
Gautam Gala <ggala@linux.ibm.com>,
Steffen Eiden <seiden@linux.ibm.com>
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 in final build
Date: Thu, 15 Oct 2026 18:54:47 +0200 [thread overview]
Message-ID: <0e51ee38-d774-4740-9984-8908fc9307a5@linux.ibm.com> (raw)
In-Reply-To: <atDyad6Dg3msWmW_@sirena.org.uk>
Am 15.10.26 um 17:34 schrieb Mark Brown:
> Hi all,
>
> In the final build, today's linux-next build (s390 defconfig) failed
> like this:
>
> /tmp/next/build/arch/s390/kvm/arm64/../gmap/kvm_mmu.c: In function 's390_kvm_mmu_prepare_memory_region':
> /tmp/next/build/arch/s390/kvm/arm64/../gmap/kvm_mmu.c:83:22: error: 'struct kvm_arch' has no member named 'migration_mode'
> 83 | if (kvm->arch.migration_mode) {
> | ^
>
>
> Caused by commit
>
> 325380d8e7893 (KVM: s390: arm64: Integrate arm on s390)
>
> I have reverted that for today.
Should also be fixed tomorrow. Sorry for the hazzle.
next prev parent reply other threads:[~2026-10-15 16:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 15:34 linux-next: build failure in final build Mark Brown
2026-10-15 16:54 ` Christian Borntraeger [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-30 15:00 Mark Brown
2026-07-31 22:03 ` Linus Walleij
2026-07-29 15:34 Mark Brown
2026-07-30 9:14 ` Mykyta Yatsenko
2026-08-03 16:35 ` Mark Brown
2026-08-04 11:35 ` Mykyta Yatsenko
2026-08-04 11:48 ` Mykyta Yatsenko
2026-08-05 20:23 ` Steven Rostedt
2026-07-13 16:48 Mark Brown
2026-07-13 18:46 ` Tyrel Datwyler
2026-07-02 18:26 Mark Brown
2026-07-03 5:04 ` Kir Chou
2026-06-15 14:43 Mark Brown
2026-06-15 16:21 ` Mark Brown
2026-05-18 16:21 Mark Brown
2026-05-18 19:24 ` Nathan Chancellor
2026-05-18 20:06 ` Linus Torvalds
2026-04-01 14:07 Mark Brown
2026-03-27 22:01 Mark Brown
2026-03-27 22:03 ` Mark Brown
2026-03-27 22:05 ` Mark Brown
2026-03-28 2:18 ` Steven Rostedt
2026-03-26 16:04 Mark Brown
2026-03-26 17:05 ` Danilo Krummrich
2026-01-19 22:30 Mark Brown
2026-01-19 22:37 ` Miguel Ojeda
2026-01-19 23:32 ` Mark Brown
2026-01-19 22:49 ` Danilo Krummrich
2026-01-20 8:36 ` Alice Ryhl
2026-01-20 10:01 ` Danilo Krummrich
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=0e51ee38-d774-4740-9984-8908fc9307a5@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=broonie@kernel.org \
--cc=ggala@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=seiden@linux.ibm.com \
/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