From: Mark Brown <broonie@kernel.org>
To: Sean Christopherson <seanjc@google.com>
Cc: Fuad Tabba <fuad.tabba@linux.dev>, Marc Zyngier <maz@kernel.org>,
Oliver Upton <oupton@kernel.org>,
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 kvm-x86 tree
Date: Wed, 16 Sep 2026 15:24:33 +0100 [thread overview]
Message-ID: <e3dc428b-7dae-4a1f-b2ca-6085b2343d8a@sirena.org.uk> (raw)
In-Reply-To: <aqqiAbgDmfQBLPTA@google.com>
[-- Attachment #1: Type: text/plain, Size: 276 bytes --]
On Wed, Sep 16, 2026 at 07:04:49AM -0700, Sean Christopherson wrote:
> The test also needs to override/define the memory region. Not fully tested, but
> I think it's this:
Thanks for checking, I'll roll your fixup into my resolution tomorrow
unless someone says otherwise.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-09-16 14:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 13:33 linux-next: build failure after merge of the kvm-x86 tree Mark Brown
2026-09-16 14:04 ` Sean Christopherson
2026-09-16 14:24 ` Mark Brown [this message]
2026-09-16 16:36 ` Oliver Upton
2026-09-16 16:43 ` Sean Christopherson
2026-09-16 16:44 ` Oliver Upton
-- strict thread matches above, loose matches on Subject: below --
2023-10-30 2:48 Stephen Rothwell
2023-10-30 10:05 ` Christian Brauner
2023-10-30 11:27 ` Paolo Bonzini
2023-10-30 20:37 ` Stephen Rothwell
2023-10-30 21:05 ` Sean Christopherson
2023-10-30 21:10 ` Stephen Rothwell
2023-10-31 13:42 ` Paolo Bonzini
2023-04-11 4:00 Stephen Rothwell
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=e3dc428b-7dae-4a1f-b2ca-6085b2343d8a@sirena.org.uk \
--to=broonie@kernel.org \
--cc=fuad.tabba@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=seanjc@google.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