From: Oliver Upton <oupton@kernel.org>
To: Sean Christopherson <seanjc@google.com>
Cc: Mark Brown <broonie@kernel.org>,
Fuad Tabba <fuad.tabba@linux.dev>, Marc Zyngier <maz@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 09:44:57 -0700 [thread overview]
Message-ID: <aqrHiTfI5QjUi_UM@kernel.org> (raw)
In-Reply-To: <aqrHIlx2F9__sLef@google.com>
On Wed, Sep 16, 2026 at 09:43:14AM -0700, Sean Christopherson wrote:
> On Wed, Sep 16, 2026, Oliver Upton wrote:
> > > In case anyone cares, I'm woefully behind on sending "thanks". These came from
> > > the prep series for enabling PPC selftests.
> > >
> > > https://lore.kernel.org/all/20260826230511.972824-1-seanjc@google.com
> > >
> > > > interacting with commit
> > > >
> > > > 6f182db39fb00 (KVM: arm64: selftests: Add ITS table save tests)
> > > >
> > > > from the kvm-arm tree. I have applied the fixup below and can carry as
> > > > needed:
> > >
> > > Given that this is in "fixes", I assume the new test will land in 7.3? If so,
> > > this is mostly my problem to deal with when sending Paolo the selftests pull
> > > (which, FWIW, I'm hoping to do this week so that it can be used as the base for
> > > PPC selftests support).
> >
> > Yeah, aim here is to have the selftest go with the fix which I'll send to
> > Paolo this week. Sorry for the churn.
>
> LOL, why are you apoligizing? You added one test, I reworked all of the core
> allocator APIs. :-D
I'm pretty sure you've conditioned everyone to endure at least one
KVM-wide rework every release ;-)
next prev parent reply other threads:[~2026-09-16 16:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 13:33 Mark Brown
2026-09-16 14:04 ` Sean Christopherson
2026-09-16 14:24 ` Mark Brown
2026-09-16 16:36 ` Oliver Upton
2026-09-16 16:43 ` Sean Christopherson
2026-09-16 16:44 ` Oliver Upton [this message]
-- 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=aqrHiTfI5QjUi_UM@kernel.org \
--to=oupton@kernel.org \
--cc=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=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
all inboxes | Powered by JetHome®