From: Marc Zyngier <maz@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Mark Brown <broonie@kernel.org>, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, kvm@vger.kernel.org,
Ricardo Koller <ricarkol@google.com>,
David Matlack <dmatlack@google.com>,
Sean Christopherson <seanjc@google.com>
Subject: Re: [PATCH] KVM: selftests: Fix build for memstress.[ch] rename
Date: Wed, 07 Dec 2022 07:54:03 +0000 [thread overview]
Message-ID: <875yentzs4.wl-maz@kernel.org> (raw)
In-Reply-To: <47b3d23b-e00e-b78f-69f4-4687f4ac607f@redhat.com>
On Wed, 07 Dec 2022 00:33:12 +0000,
Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> On 12/6/22 21:42, Stephen Rothwell wrote:
> > Thanks for that. I have added that as a merge fix patch to the kvm-arm
> > merge. I assume this will be fixed up when that tree is merged into
> > the kvm tree.
>
> Yes, I'll push as soon as I get confirmation that my own resolution is
> correct.
As I said in [1], things do build once you add [2] to the mix. I
haven't had time to test the tests, but that shouldn't hold the push
into -next.
M.
[1] https://lore.kernel.org/all/86lenkl4d0.wl-maz@kernel.org
[2] https://lore.kernel.org/r/20221206181506.252537-1-broonie@kernel.org
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2022-12-07 7:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 17:59 [PATCH] KVM: selftests: Fix build for memstress.[ch] rename Mark Brown
2022-12-06 20:42 ` Stephen Rothwell
2022-12-07 0:33 ` Paolo Bonzini
2022-12-07 1:44 ` Sean Christopherson
2022-12-07 7:54 ` Marc Zyngier [this message]
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=875yentzs4.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=broonie@kernel.org \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=ricarkol@google.com \
--cc=seanjc@google.com \
--cc=sfr@canb.auug.org.au \
--cc=shuah@kernel.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