public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Oliver Upton <oliver.upton@linux.dev>,
	Paolo Bonzini <pbonzini@redhat.com>,
	James Morse <james.morse@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>,
	kvmarm@lists.linux.dev, kvm@vger.kernel.org
Subject: Re: [GIT PULL] KVM/arm64 fixes for 6.7, part #2
Date: Fri, 22 Dec 2023 13:34:09 +0000	[thread overview]
Message-ID: <441ff2c753fbfd69a60e93031070b09e@kernel.org> (raw)
In-Reply-To: <ffbca4ce-7386-469b-952c-f33e2ba42a51@sirena.org.uk>

On 2023-12-22 13:26, Mark Brown wrote:
> On Fri, Dec 22, 2023 at 01:16:41PM +0000, Marc Zyngier wrote:
> 
>> > Oliver, should your tree be in -next?
> 
>> No, we don't have the KVM/arm64 fixes in -next.
> 
> I see it's not, I'm asking if it should be - given the latencies
> involved it seems like it'd be helpful for keeping -next working.

This is on purpose. We use -next for, well, the next release,
and not as a band-aid for some other purpose. If you think things
don't get merged quickly enough, please take it with the person
processing the PRs (Paolo).

> 
>> And we have another two weeks to release, so ample amount of
>> time until Paolo picks up the PR.
> 
> Sure, but we do also have the holidays and also the fact that it's a
> build failure in a configuration used by some of the CIs means that
> we've got a bunch of testing that simply hasn't been happening for a
> couple of weeks now.

Given that most of the KVM tests are usually more broken than
the kernel itself, I'm not losing much sleep over it.

         M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2023-12-22 13:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18 19:17 [GIT PULL] KVM/arm64 fixes for 6.7, part #2 Oliver Upton
2023-12-22 13:09 ` Mark Brown
2023-12-22 13:16   ` Marc Zyngier
2023-12-22 13:26     ` Mark Brown
2023-12-22 13:34       ` Marc Zyngier [this message]
2023-12-22 14:20         ` Mark Brown
2023-12-22 23:25           ` Paolo Bonzini
2023-12-22 23:04 ` Paolo Bonzini

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=441ff2c753fbfd69a60e93031070b09e@kernel.org \
    --to=maz@kernel.org \
    --cc=broonie@kernel.org \
    --cc=james.morse@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=oliver.upton@linux.dev \
    --cc=pbonzini@redhat.com \
    --cc=suzuki.poulose@arm.com \
    --cc=yuzenghui@huawei.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