From: Oliver Upton <oliver.upton@linux.dev>
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: Marc Zyngier <maz@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, kvmarm@lists.linux.dev
Subject: Re: [PATCH v2 0/3] KVM: selftests: Fixes for broken tests
Date: Thu, 23 Mar 2023 17:38:39 +0000 [thread overview]
Message-ID: <ZByOn79zokUpLGSs@linux.dev> (raw)
In-Reply-To: <4eca298b-411f-e6db-04d2-e8963a0e5d98@arm.com>
Hey Ryan,
On Thu, Mar 23, 2023 at 12:56:18PM +0000, Ryan Roberts wrote:
> Hi Oliver,
>
> Just a polite nudge on this: I was originally hoping to get these into 6.3 since
> I thought they were fairly uncontroversial and clearly fixing bugs. What are my
> chances?
Yes, your changes are indeed uncontroversial :) At least for me, fixes to
selftests take a strictly lower priority than fixes to the kernel outside of
a merge window. AFAICT, only LPA systems are affected by the changes here and
I'm not aware of any of those out in the wild.
So, unless there is a burning issue, I'd like to defer these patches to the
6.4 merge window. Nonetheless, it all looks good to me:
Reviewed-by: Oliver Upton <oliver.upton@linux.dev>
--
Thanks,
Oliver
next prev parent reply other threads:[~2023-03-23 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 11:09 [PATCH v2 0/3] KVM: selftests: Fixes for broken tests Ryan Roberts
2023-03-08 11:09 ` [PATCH v2 1/3] KVM: selftests: Fixup config fragment for access_tracking_perf_test Ryan Roberts
2023-03-24 15:32 ` Sean Christopherson
2023-03-08 11:09 ` [PATCH v2 2/3] KVM: selftests: arm64: Fix pte encode/decode for PA bits > 48 Ryan Roberts
2023-03-08 11:09 ` [PATCH v2 3/3] KVM: selftests: arm64: Fix ttbr0_el1 encoding " Ryan Roberts
2023-03-23 12:56 ` [PATCH v2 0/3] KVM: selftests: Fixes for broken tests Ryan Roberts
2023-03-23 17:38 ` Oliver Upton [this message]
2023-03-23 18:56 ` Marc Zyngier
2023-03-24 9:04 ` Ryan Roberts
2023-03-30 18:37 ` Marc Zyngier
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=ZByOn79zokUpLGSs@linux.dev \
--to=oliver.upton@linux.dev \
--cc=kvmarm@lists.linux.dev \
--cc=linux-kselftest@vger.kernel.org \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=ryan.roberts@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.