From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CB77EC31E40 for ; Fri, 9 Aug 2019 07:37:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AE77B206DF for ; Fri, 9 Aug 2019 07:37:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2405906AbfHIHh2 (ORCPT ); Fri, 9 Aug 2019 03:37:28 -0400 Received: from mail-wm1-f66.google.com ([209.85.128.66]:34123 "EHLO mail-wm1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2405893AbfHIHhY (ORCPT ); Fri, 9 Aug 2019 03:37:24 -0400 Received: by mail-wm1-f66.google.com with SMTP id e8so5317730wme.1 for ; Fri, 09 Aug 2019 00:37:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Uupbz8YTA+5+vl0Fvj16ZEysWFtXXYG59jnDaWr/XA8=; b=WhO7tFNIHb9vjjSpgzCGt8KG6IRBiYnvBbPlKs8m+Dv7L/CzWrgWGchGKOC59Fl1ev 8Oj+pGhwP1RdfQfP79kMhVG1pqptU/ETMQM+/oV73vTFeU5nmLOMd9+iXpj+7LYjGX0D MPZ97RWZkbg+IwIiL9bdZYBdTue7o296BU6G0nTAPlnLkXw2OC8naDWW19whUqsRd9jM GHRzfY8pYlQdyLMwPyGEEHBloOhxWJ3rlZUIL+eKcYg/ez0jwE7Hpm2G+Y9Qd/76xapD a4Cl7y9klFpLXsEomNDQ/AUpwYw0b6cRnJ6M/oY6sC5hO0JCBtVs3CBOp8rJKLyXI99e Qxyg== X-Gm-Message-State: APjAAAVzpmzJ5qY6IW4IeSPoivT8wwsZv1/O49GNQ0qHiyqqkzyu2Qhv UlhgmFEWbzXrWYS5VKkPjULbCkwiVHg= X-Google-Smtp-Source: APXvYqxpCCW54J3fN4T1bkdCwN0FL2+ouWimhzANbhGNXOTpOA9eMsxirOHRMFEtnyEluH/UmRwhLQ== X-Received: by 2002:a1c:99c6:: with SMTP id b189mr9246872wme.57.1565336242632; Fri, 09 Aug 2019 00:37:22 -0700 (PDT) Received: from ?IPv6:2001:b07:6468:f312:b42d:b492:69df:ed61? ([2001:b07:6468:f312:b42d:b492:69df:ed61]) by smtp.gmail.com with ESMTPSA id 4sm227355416wro.78.2019.08.09.00.37.21 (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Fri, 09 Aug 2019 00:37:22 -0700 (PDT) Subject: Re: [PATCH v4 00/20] KVM RISC-V Support To: Paul Walmsley Cc: Anup Patel , Palmer Dabbelt , Radim K , Daniel Lezcano , Thomas Gleixner , Atish Patra , Alistair Francis , Damien Le Moal , Christoph Hellwig , Anup Patel , "kvm@vger.kernel.org" , "linux-riscv@lists.infradead.org" , "linux-kernel@vger.kernel.org" References: <20190807122726.81544-1-anup.patel@wdc.com> <4a991aa3-154a-40b2-a37d-9ee4a4c7a2ca@redhat.com> From: Paolo Bonzini Openpgp: preference=signencrypt Message-ID: <2ea0c656-bd7e-ae79-1f8e-6b60374ccc6e@redhat.com> Date: Fri, 9 Aug 2019 09:37:20 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/08/19 03:35, Paul Walmsley wrote: > On Thu, 8 Aug 2019, Paolo Bonzini wrote: > >> However, for Linux releases after 5.4 I would rather get pull requests >> for arch/riscv/kvm from Anup and Atish without involving the RISC-V >> tree. Of course, they or I will ask for your ack, or for a topic >> branch, on the occasion that something touches files outside their >> maintainership area. This is how things are already being handled for >> ARM, POWER and s390 and it allows me to handle conflicts in common KVM >> files before they reach Linus; these are more common than conflicts in >> arch files. If you have further questions on git and maintenance >> workflows, just ask! > > In principle, that's fine with me, as long as the arch/riscv maintainers > and mailing lists are kept in the loop. We already do something similar > to this for the RISC-V BPF JIT. However, I'd like this to be explicitly > documented in the MAINTAINERS file, as it is for BPF. It looks like it > isn't for ARM, POWER, or S390, either looking at MAINTAINERS or > spot-checking scripts/get_maintainer.pl: > > $ scripts/get_maintainer.pl -f arch/s390/kvm/interrupt.c > Christian Borntraeger (supporter:KERNEL VIRTUAL MACHINE for s390 (KVM/s390)) > Janosch Frank (supporter:KERNEL VIRTUAL MACHINE for s390 (KVM/s390)) > David Hildenbrand (reviewer:KERNEL VIRTUAL MACHINE for s390 (KVM/s390)) > Cornelia Huck (reviewer:KERNEL VIRTUAL MACHINE for s390 (KVM/s390)) > Heiko Carstens (supporter:S390) > Vasily Gorbik (supporter:S390) > linux-s390@vger.kernel.org (open list:KERNEL VIRTUAL MACHINE for s390 (KVM/s390)) > linux-kernel@vger.kernel.org (open list) > $ > > Would you be willing to send a MAINTAINERS patch to formalize this > practice? Ah, I see, in the MAINTAINERS entry KERNEL VIRTUAL MACHINE FOR RISC-V (KVM/riscv) M: Anup Patel R: Atish Patra L: linux-riscv@lists.infradead.org T: git git://github.com/avpatel/linux.git S: Maintained F: arch/riscv/include/uapi/asm/kvm* F: arch/riscv/include/asm/kvm* F: arch/riscv/kvm/ the L here should be kvm@vger.kernel.org. arch/riscv/kvm/ files would still match RISC-V ARCHITECTURE and therefore linux-riscv@lists.infradead.org would be CCed. Unlike other subsystems, for KVM I ask the submaintainers to include the patches in their pull requests, which is why you saw no kvm@vger entry for KVM/s390. However, it's probably a good idea to add it and do the same for RISC-V. Is that what you meant? Paolo