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=-2.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no 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 57850C0650F for ; Fri, 9 Aug 2019 01:35:53 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 2CB372171F for ; Fri, 9 Aug 2019 01:35:53 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="bmEOioP9"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=sifive.com header.i=@sifive.com header.b="bTgJPRLs" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2CB372171F Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=sifive.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:Message-ID: In-Reply-To:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=CSf36jXXDjN4s48ox5cfFUOLbGdArSoCtdofcrwgo+w=; b=bmEOioP9LGlH5i k90zG0zQMBj6YyJUCe12okgEypJzam8u6pbgcsz2yuI9pX9t2+Nlh5RULiZLnGGClnvmSfKd8N75F JxU3ZEibvk9i5CSynXz1n3ljQ2Mazhy3FQ6VdpKSkwhqCWl0oGz8MsaSNelwqtbRgI+Ab4N0q4vt+ b0kE7z7xv9NmE55Rd5TsY/89YjBimZX6qn248uUCeL4aiNs17fAGoYDHpRh2PH0gBdhzWo27WkLwQ hTAPc1WZHuczQHS6U0GTGOsAE9yUSvxiPxSLfZaOXpNFRsWAGqO9bFQg3+2J1o2ToUnBNkt6doXDs VABt2iPFciCG106zNKrA==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hvtop-00033S-0I; Fri, 09 Aug 2019 01:35:47 +0000 Received: from mail-ot1-x344.google.com ([2607:f8b0:4864:20::344]) by bombadil.infradead.org with esmtps (Exim 4.92 #3 (Red Hat Linux)) id 1hvtok-00032O-OD for linux-riscv@lists.infradead.org; Fri, 09 Aug 2019 01:35:43 +0000 Received: by mail-ot1-x344.google.com with SMTP id z17so8134075otk.13 for ; Thu, 08 Aug 2019 18:35:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=date:from:to:cc:subject:in-reply-to:message-id:references :user-agent:mime-version; bh=oT9+0FRk0XTKJRYl2Q4sGfwT0uvjls0OapEyGavcfH0=; b=bTgJPRLs2KrCeHGbSsBv9KpIvMO4o+oQxiwzpIwFpWL81l/u3yEfGm+OY2bjOE74R0 9yYJw3nQi+IWuSeNzJUo1TO+upgefj8sw6thmlg87ONcHJ3BejfoutIAglkH2W1wIIzm 41roYeNsXFspvh63xyi/HLeMW1uplON18rcefr8C4qTXVAdZ4fVmBYwo7wcmbvU7vJ1N vp2AVdy+3DnZW7iP3rOXxmt/us1b4gnH40TgQVxUcai+W8og/9GcqaEgP48JE/ttGIst PBl1Nr3HEwTHZ++nPN65TvwKesqbXB1Bgw3u07ro5xdvOsdOgWIEOrkOGNsEP3Z63dR/ OAEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=oT9+0FRk0XTKJRYl2Q4sGfwT0uvjls0OapEyGavcfH0=; b=GWHekNo6ya+WqEqZEf7h6W4AiDwRf3sEwIcpjXjsFvsVyMymUVUTdDN5+VzO8yzhT3 5u/jFtV2ThUSb+URr+YzcFi46Awc/L84iin1LQign2FgYnc4s2HtEQK+hbNdd5NizpEM uhnBNy7qUDwBuT+t8wZnEt+9ynJk+3Bik73E9aMfWSKkyi0fEa6H3qtL4NgIkiNarvBS yTZakLYF6KYloZg7TBXnqYG4o7wX/uwpfGbNpQs7SXynoYveixYgTBNKr+VaP2yhNTRL Sxzp/4d/w3SSz0Mz2Gu5KyPUt+O3yt6LBi03kas/lFQf8RUcjne7YzrPtDLmwAUgenpu h/nQ== X-Gm-Message-State: APjAAAVurJovdybjD09q1aRHZCVyfsN5Tgo0H17OhrPO08rjLsQJje49 ZllzSsySuDsHGdusIhk4OWAOTY8pEgY= X-Google-Smtp-Source: APXvYqz6ICJH3+/BdftjNoVT6B/6SpEFAG0akxiwAjeOkWh6cvUY64FsLO+6gp/jqLLJBXFNGB3+Kw== X-Received: by 2002:a6b:641a:: with SMTP id t26mr18476138iog.3.1565314539454; Thu, 08 Aug 2019 18:35:39 -0700 (PDT) Received: from localhost (c-73-95-159-87.hsd1.co.comcast.net. [73.95.159.87]) by smtp.gmail.com with ESMTPSA id z6sm2274953ioi.8.2019.08.08.18.35.38 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Thu, 08 Aug 2019 18:35:38 -0700 (PDT) Date: Thu, 8 Aug 2019 18:35:38 -0700 (PDT) From: Paul Walmsley X-X-Sender: paulw@viisi.sifive.com To: Paolo Bonzini Subject: Re: [PATCH v4 00/20] KVM RISC-V Support In-Reply-To: Message-ID: References: <20190807122726.81544-1-anup.patel@wdc.com> <4a991aa3-154a-40b2-a37d-9ee4a4c7a2ca@redhat.com> User-Agent: Alpine 2.21.9999 (DEB 301 2018-08-15) MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190808_183542_802676_3DFCA16E X-CRM114-Status: UNSURE ( 9.76 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Damien Le Moal , Palmer Dabbelt , Daniel Lezcano , "kvm@vger.kernel.org" , Radim K , Anup Patel , Anup Patel , "linux-kernel@vger.kernel.org" , Christoph Hellwig , Atish Patra , Alistair Francis , Thomas Gleixner , "linux-riscv@lists.infradead.org" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-riscv" Errors-To: linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org 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? - Paul _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv