All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Huacai Chen <chenhc@lemote.com>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>, kvm <kvm@vger.kernel.org>,
	"open list:MIPS" <linux-mips@vger.kernel.org>,
	Fuxin Zhang <zhangfx@lemote.com>
Subject: Re: [PATCH V5 15/15] MAINTAINERS: Update KVM/MIPS maintainers
Date: Mon, 18 May 2020 10:42:14 +0200	[thread overview]
Message-ID: <CAHiYmc6qnvEhgX8BOhuUkQcfnLzBf_1hqoW=GKGh26KpQU5HLQ@mail.gmail.com> (raw)
In-Reply-To: <1a22adb0-0b7a-24a3-e762-7b9919a70a8e@redhat.com>

суб, 16. мај 2020. у 13:55 Paolo Bonzini <pbonzini@redhat.com> је написао/ла:
>
> On 16/05/20 11:36, Huacai Chen wrote:
> >> I'm happy to see you taking care of the KVM part. So how is your plan
> >> to handle patches ? Do want to collect them and send pull requests to
> >> me ? Or should I just pick them up with your Acked-by ?
> > I think we can only use the second method, because both Aleksandar and
> > me don't have a kernel tree in kernel.org now.
>
> If you don't mind, I generally prefer to have MIPS changs submitted
> through the KVM tree, because KVM patches rarely have intrusive changes
> in generic arch files.  It's more common to have generic KVM patches
> that require touching all architectures.
>

To me, Paolo's workflow seems reasonable and efficient from practical
point of view. No unnecessary multitude of repeated series or pull sending,
and no single person is burdened with majority of work being done just by
himself for any given case of series like this one. Also, it looks to me it is
quite efficient wrt possible conflict and rebase issues, that will be taken
care by both KVM/MIPS and KVM/general submitters/maintainers.

I suggest we keep Paolo's workflow plan for this series, but, more
importantly, if you guys all agree, in future as well.

Sincerely,
Aleksandar

> For 5.8 I don't have anything planned that could cause conflicts, so
> this time it doesn't matter; but I can pick these up too if Thomas acks
> patches 6, 12 and 14.
>
> Thanks,
>
> Paolo
>

      parent reply	other threads:[~2020-05-18  8:42 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13  8:42 [PATCH V5 00/15] KVM: MIPS: Add Loongson-3 support (Host Side) Huacai Chen
2020-05-13  8:42 ` [PATCH V5 01/15] KVM: MIPS: Define KVM_ENTRYHI_ASID to cpu_asid_mask(&boot_cpu_data) Huacai Chen
2020-05-19 11:49   ` Sasha Levin
2020-05-13  8:42 ` [PATCH V5 02/15] KVM: MIPS: Fix VPN2_MASK definition for variable cpu_vmbits Huacai Chen
2020-05-13  8:42 ` [PATCH V5 03/15] KVM: MIPS: Increase KVM_MAX_VCPUS and KVM_USER_MEM_SLOTS to 16 Huacai Chen
2020-05-13  8:42 ` [PATCH V5 04/15] KVM: MIPS: Add EVENTFD support which is needed by VHOST Huacai Chen
2020-05-13  8:42 ` [PATCH V5 05/15] KVM: MIPS: Use lddir/ldpte instructions to lookup gpa_mm.pgd Huacai Chen
2020-05-13  8:42 ` [PATCH V5 06/15] KVM: MIPS: Introduce and use cpu_guest_has_ldpte Huacai Chen
2020-05-16 15:37   ` Thomas Bogendoerfer
2020-05-13  8:42 ` [PATCH V5 07/15] KVM: MIPS: Use root tlb to control guest's CCA for Loongson-3 Huacai Chen
2020-05-13  8:42 ` [PATCH V5 08/15] KVM: MIPS: Let indexed cacheops cause guest exit on Loongson-3 Huacai Chen
2020-05-13  8:42 ` [PATCH V5 09/15] KVM: MIPS: Add more types of virtual interrupts Huacai Chen
2020-05-13  8:42 ` [PATCH V5 10/15] KVM: MIPS: Add Loongson-3 Virtual IPI interrupt support Huacai Chen
2020-05-13  8:42 ` [PATCH V5 11/15] KVM: MIPS: Add CPUCFG emulation for Loongson-3 Huacai Chen
2020-05-13  8:42 ` [PATCH V5 12/15] KVM: MIPS: Add CONFIG6 and DIAG registers emulation Huacai Chen
2020-05-14  7:45   ` Aleksandar Markovic
2020-05-16 15:36   ` Thomas Bogendoerfer
2020-05-13  8:42 ` [PATCH V5 13/15] KVM: MIPS: Add more MMIO load/store instructions emulation Huacai Chen
2020-05-13  8:42 ` [PATCH V5 14/15] KVM: MIPS: Enable KVM support for Loongson-3 Huacai Chen
2020-05-14  7:46   ` Aleksandar Markovic
2020-05-16 15:35   ` Thomas Bogendoerfer
2020-05-13  8:42 ` [PATCH V5 15/15] MAINTAINERS: Update KVM/MIPS maintainers Huacai Chen
2020-05-14  7:47   ` Aleksandar Markovic
2020-05-14 13:33   ` Jiaxun Yang
2020-05-15  1:50     ` Huacai Chen
2020-05-15 21:13       ` Thomas Bogendoerfer
2020-05-16  9:36         ` Huacai Chen
2020-05-16 11:55           ` Paolo Bonzini
2020-05-16 15:38             ` Thomas Bogendoerfer
2020-05-17  5:50               ` Huacai Chen
2020-05-18  8:42             ` Aleksandar Markovic [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='CAHiYmc6qnvEhgX8BOhuUkQcfnLzBf_1hqoW=GKGh26KpQU5HLQ@mail.gmail.com' \
    --to=aleksandar.qemu.devel@gmail.com \
    --cc=chenhc@lemote.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=tsbogend@alpha.franken.de \
    --cc=zhangfx@lemote.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.