From: Paolo Bonzini <pbonzini@redhat.com>
To: Palmer Dabbelt <palmerdabbelt@google.com>
Cc: anup@brainfault.org, kvm@vger.kernel.org,
kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org
Subject: Re: [GIT PULL] KVM/riscv for 5.16
Date: Thu, 7 Oct 2021 08:59:28 +0200 [thread overview]
Message-ID: <42039591-c445-9298-607a-76efe875eb53@redhat.com> (raw)
In-Reply-To: <mhng-03b25a51-3491-4bb7-9e17-1b32fc97b7ff@palmerdabbelt-glaptop>
On 06/10/21 18:42, Palmer Dabbelt wrote:
> On Tue, 05 Oct 2021 01:25:41 PDT (-0700), pbonzini@redhat.com wrote:
>> On 05/10/21 09:55, Anup Patel wrote:
>>> git://github.com/kvm-riscv/linux.git tags/kvm-riscv-5.16-1
>>
>> Pulled, thanks!
>
> Thanks!
>
> IIUC how this generally works is that you pull these KVM-specific patch
> sets and I don't, which means they'll get tested on my end as they loop
> back through linux-next. I'm fine with however this usually works, just
> trying to make sure we're on the same page as this is my first time
> being this close to another tree.
Generally speaking, Anup as the maintainer is responsible for things not
breaking. I do a cross-compile to check against changes to KVM common
code in virt/kvm, but otherwise just take his tree and send it out to
Linus. Once selftests are in, I will also be able to run them under
QEMU, again to check that changes to virt/kvm/ do not break RISC-V.
Paolo
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2021-10-07 7:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 7:55 [GIT PULL] KVM/riscv for 5.16 Anup Patel
2021-10-05 8:25 ` Paolo Bonzini
2021-10-06 16:42 ` Palmer Dabbelt
2021-10-07 6:59 ` Paolo Bonzini [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=42039591-c445-9298-607a-76efe875eb53@redhat.com \
--to=pbonzini@redhat.com \
--cc=anup@brainfault.org \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmerdabbelt@google.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