From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
Anup Patel <anup@brainfault.org>,
kvm@vger.kernel.org
Subject: Re: Getting the kvm-riscv tree in next
Date: Fri, 21 Apr 2023 18:50:39 -0700 [thread overview]
Message-ID: <ZEM9b13OTjq9+4ZY@google.com> (raw)
In-Reply-To: <100c4e47-9d8d-8b3a-b70b-c0498febf23c@redhat.com>
On Sat, Apr 22, 2023, Paolo Bonzini wrote:
> On 4/21/23 21:10, Oliver Upton wrote:
> > I've also noticed that for the past few kernel release cycles you've
> > used an extremely late rc (i.e. -rc7 or -rc8), which I fear only
> > draws more scrutiny.
>
> Heh, I just wrote the same thing to Anup. In particular, having kvm-riscv
> in next (either directly or by sending early pull requests to me) would have
> helped me understand the conflicts between the core and KVM trees for
> RISC-V, because Stephen Rothwell would have alerted me about them.
Speaking of not-early pull requests, I'm not going to get the x86 pull requests
sent until Monday. Everything has been in place for a few weeks now, but I buried
myself too deep in UPM/restrictedmem stuff and ran out of time today (and I don't
trust my brain to not make stupid mistakes at this point).
next prev parent reply other threads:[~2023-04-22 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 19:10 Getting the kvm-riscv tree in next Oliver Upton
2023-04-21 23:48 ` Paolo Bonzini
2023-04-22 1:50 ` Sean Christopherson [this message]
2023-04-22 7:30 ` Anup Patel
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=ZEM9b13OTjq9+4ZY@google.com \
--to=seanjc@google.com \
--cc=anup@brainfault.org \
--cc=kvm@vger.kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.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