From: Marc Zyngier <maz@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
reijiw@google.com, dmatlack@google.com, james.morse@arm.com,
suzuki.poulose@arm.com, yuzenghui@huawei.com,
kvmarm@lists.linux.dev, kvm@vger.kernel.org
Subject: Re: [GIT PULL] KVM/arm64 fixes for 6.3, part #2
Date: Mon, 27 Mar 2023 15:15:38 +0100 [thread overview]
Message-ID: <86sfdqwa9h.wl-maz@kernel.org> (raw)
In-Reply-To: <49385a34-6ad7-255d-68d9-6b41a76f01df@redhat.com>
On Mon, 27 Mar 2023 14:59:19 +0100,
Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> On 3/27/23 13:39, Marc Zyngier wrote:
> >> Paolo,
> >>
> >> Pinging this PR in case you missed it, the issues around host page table walks
> >> are particularly urgent as the race on host page table teardown has been
> >> reproduced on some setups.
> > If we don't hear from Paolo shortly, I suggest we route this via the
> > arm64 tree.
>
> It missed the pull request I sent on March 17th by a few hours. I
> have queued it now and will send it to Linus later today.
Maybe you could help us here and state what is your schedule when it
comes to sending these pull requests? It would certainly help
coordinate and avoid wasting 10+ days to get things merged.
I appreciate that you don't need nor want to wait for us to send
something to Linus, but if we know when the train is departing, we can
make sure we're standing on the platform early enough.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2023-03-27 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 3:09 [GIT PULL] KVM/arm64 fixes for 6.3, part #2 Oliver Upton
2023-03-24 18:16 ` Oliver Upton
2023-03-27 11:39 ` Marc Zyngier
2023-03-27 13:59 ` Paolo Bonzini
2023-03-27 14:15 ` Marc Zyngier [this message]
2023-03-27 14:22 ` 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=86sfdqwa9h.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dmatlack@google.com \
--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=reijiw@google.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--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