From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
Anup Patel <anup@brainfault.org>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Palmer Dabbelt <palmer@rivosinc.com>,
Andrew Jones <ajones@ventanamicro.com>,
Atish Patra <atishp@atishpatra.org>,
Atish Patra <atishp@rivosinc.com>,
KVM General <kvm@vger.kernel.org>,
"open list:KERNEL VIRTUAL MACHINE FOR RISC-V (KVM/riscv)"
<kvm-riscv@lists.infradead.org>,
linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [GIT PULL] KVM/riscv changes for 6.9
Date: Mon, 11 Mar 2024 15:10:17 +0100 [thread overview]
Message-ID: <6091398f-a2b3-4dc9-9f33-d7459a0a9594@redhat.com> (raw)
In-Reply-To: <ZesxeoyFZUeo-Z9F@google.com>
On 3/8/24 16:40, Sean Christopherson wrote:
> You're missing the point. I don't care when patches land in the RISC-V tree, nor
> do I care that you made a last minute tweak to fix a bug. I care when commits
> show up in linux-next, and*none* of these commits were in linux-next until
> yesterday.
>
> $ git tag -l --contains 2c5af1c8460376751d57c50af88a053a3b869926
> next-20240307
> next-20240308
>
> The*entire* purpose of linux-next is to integrate*all* work destined for the
> next kernel into a single tree, so that conflicts, bugs, etc. can be found and
> fixed*before* the next merge window.
Indeed, and this is more important as more work is routed towards
different trees. At this point we have 5 more or less active
architectures, and especially in selftests land it's important to
coordinate with each other.
Anup, ideally, when you say that a patch is "queued" it should only be a
short time before you're ready to send it to me - and that means putting
it in a place where linux-next picks it up. For x86 I generally compile
test and run kvm-unit-tests on one of Intel or AMD, and leave the
remaining tests for later (because they take a day or two), but in
general it's a matter of days before linux-next get the patches.
Paolo
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-03-11 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 6:45 [GIT PULL] KVM/riscv changes for 6.9 Anup Patel
2024-03-07 17:43 ` Sean Christopherson
2024-03-07 18:42 ` Sean Christopherson
2024-03-08 5:27 ` Anup Patel
2024-03-08 15:40 ` Sean Christopherson
2024-03-11 14:10 ` Paolo Bonzini [this message]
2024-03-12 6:51 ` Anup Patel
2024-03-08 7:53 ` Andrew Jones
2024-03-11 14:19 ` 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=6091398f-a2b3-4dc9-9f33-d7459a0a9594@redhat.com \
--to=pbonzini@redhat.com \
--cc=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=atishp@atishpatra.org \
--cc=atishp@rivosinc.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=seanjc@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;
as well as URLs for NNTP newsgroup(s).