From: Paolo Bonzini <pbonzini@redhat.com>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, kvm <kvm@vger.kernel.org>,
Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>,
seanjc@google.com, "open list:MIPS" <linux-mips@vger.kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Subject: Re: [PATCH 2/4] KVM: MIPS: rework flush_shadow_* callbacks into one that prepares the flush
Date: Tue, 6 Apr 2021 08:05:40 +0200 [thread overview]
Message-ID: <510e59e7-91b0-6754-8fb5-6a936ef47b3c@redhat.com> (raw)
In-Reply-To: <CAAhV-H72z9DbbV=_fEhCeeOaP8fQ_qtr4rQMD=f5n08ekG=Ygw@mail.gmail.com>
On 06/04/21 03:36, Huacai Chen wrote:
>> I tried the merge and it will be enough for Linus to remove
>> arch/mips/kvm/trap_emul.c. So I will leave it as is, but next time I'd
>> prefer KVM MIPS changes to go through either my tree or a common topic
>> branch.
> Emmm, the TE removal series is done by Thomas, not me.:)
Sure, sorry if the sentence sounded like it was directed to you. No
matter who wrote the code, synchronization between trees is only the
maintainers' task. :)
Paolo
next prev parent reply other threads:[~2021-04-06 6:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 15:58 [PATCH 0/4] KVM: MIPS: cleanup TLB flushing callbacks Paolo Bonzini
2021-04-02 15:58 ` [PATCH 1/4] KVM: constify kvm_arch_flush_remote_tlbs_memslot Paolo Bonzini
2021-04-03 2:28 ` Huacai Chen
2021-04-02 15:58 ` [PATCH 2/4] KVM: MIPS: rework flush_shadow_* callbacks into one that prepares the flush Paolo Bonzini
2021-04-03 2:31 ` Huacai Chen
2021-04-03 7:08 ` Paolo Bonzini
2021-04-03 10:43 ` Paolo Bonzini
2021-04-06 1:36 ` Huacai Chen
2021-04-06 6:05 ` Paolo Bonzini [this message]
2021-04-06 11:39 ` Thomas Bogendoerfer
2021-04-06 11:55 ` Paolo Bonzini
2021-04-02 15:58 ` [PATCH 3/4] KVM: MIPS: let generic code call prepare_flush_shadow Paolo Bonzini
2021-04-02 15:58 ` [PATCH 4/4] KVM: MIPS: defer flush to generic MMU notifier code 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=510e59e7-91b0-6754-8fb5-6a936ef47b3c@redhat.com \
--to=pbonzini@redhat.com \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=chenhuacai@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=seanjc@google.com \
--cc=tsbogend@alpha.franken.de \
/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).