From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46719) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bei7R-0006UC-4e for qemu-devel@nongnu.org; Tue, 30 Aug 2016 08:26:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bei7M-0008Bs-25 for qemu-devel@nongnu.org; Tue, 30 Aug 2016 08:26:20 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:59515) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bei7L-0008Bc-PM for qemu-devel@nongnu.org; Tue, 30 Aug 2016 08:26:15 -0400 Received: from pps.filterd (m0098410.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.11/8.16.0.11) with SMTP id u7UCON6a032765 for ; Tue, 30 Aug 2016 08:26:14 -0400 Received: from e06smtp11.uk.ibm.com (e06smtp11.uk.ibm.com [195.75.94.107]) by mx0a-001b2d01.pphosted.com with ESMTP id 255364r7v1-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Tue, 30 Aug 2016 08:26:14 -0400 Received: from localhost by e06smtp11.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 30 Aug 2016 13:26:09 +0100 Received: from b06cxnps4075.portsmouth.uk.ibm.com (d06relay12.portsmouth.uk.ibm.com [9.149.109.197]) by d06dlp03.portsmouth.uk.ibm.com (Postfix) with ESMTP id F110C1B08077 for ; Tue, 30 Aug 2016 13:27:47 +0100 (BST) Received: from d06av07.portsmouth.uk.ibm.com (d06av07.portsmouth.uk.ibm.com [9.149.37.248]) by b06cxnps4075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id u7UCQ55D65536032 for ; Tue, 30 Aug 2016 12:26:05 GMT Received: from d06av07.portsmouth.uk.ibm.com (localhost [127.0.0.1]) by d06av07.portsmouth.uk.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id u7UCQ5k6015625 for ; Tue, 30 Aug 2016 08:26:05 -0400 Date: Tue, 30 Aug 2016 14:26:04 +0200 From: Cornelia Huck In-Reply-To: <87a8fucx33.fsf@dusky.pond.sub.org> References: <87mw8rumhb.fsf@blackfin.pond.sub.org> <87y4s8h5rh.fsf@blackfin.pond.sub.org> <876132olyi.fsf@blackfin.pond.sub.org> <87a8fucx33.fsf@dusky.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20160830142604.7c94b8b5.cornelia.huck@de.ibm.com> Subject: Re: [Qemu-devel] MAINTAINERS leaves too many files uncovered List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: qemu-devel On Tue, 30 Aug 2016 13:31:12 +0200 Markus Armbruster wrote: > >> Full list of unmaintained files now: (...) > include/standard-headers/asm-s390/kvm_virtio.h > include/standard-headers/asm-s390/virtio-ccw.h > include/standard-headers/asm-x86/hyperv.h > include/standard-headers/linux/if_ether.h > include/standard-headers/linux/input-event-codes.h > include/standard-headers/linux/input.h > include/standard-headers/linux/pci_regs.h > include/standard-headers/linux/types.h > include/standard-headers/linux/virtio_9p.h > include/standard-headers/linux/virtio_balloon.h > include/standard-headers/linux/virtio_blk.h > include/standard-headers/linux/virtio_config.h > include/standard-headers/linux/virtio_console.h > include/standard-headers/linux/virtio_gpu.h > include/standard-headers/linux/virtio_ids.h > include/standard-headers/linux/virtio_input.h > include/standard-headers/linux/virtio_net.h > include/standard-headers/linux/virtio_pci.h > include/standard-headers/linux/virtio_ring.h > include/standard-headers/linux/virtio_rng.h > include/standard-headers/linux/virtio_scsi.h > include/standard-headers/linux/virtio_types.h I don't think standard-headers can really be 'maintained', as they are essentially imported by a script. And while there's a certain overlap, the maintainer of a Linux header file is not neccessarily a qemu developer. (...) > linux-headers/COPYING > linux-headers/README > linux-headers/asm-arm/kvm.h > linux-headers/asm-arm/kvm_para.h > linux-headers/asm-arm/unistd.h > linux-headers/asm-arm64/kvm.h > linux-headers/asm-arm64/kvm_para.h > linux-headers/asm-arm64/unistd.h > linux-headers/asm-generic/kvm_para.h > linux-headers/asm-mips/kvm.h > linux-headers/asm-mips/kvm_para.h > linux-headers/asm-mips/unistd.h > linux-headers/asm-powerpc/epapr_hcalls.h > linux-headers/asm-powerpc/kvm.h > linux-headers/asm-powerpc/kvm_para.h > linux-headers/asm-powerpc/unistd.h > linux-headers/asm-s390/kvm.h > linux-headers/asm-s390/kvm_para.h > linux-headers/asm-s390/unistd.h > linux-headers/asm-x86/hyperv.h > linux-headers/asm-x86/kvm.h > linux-headers/asm-x86/kvm_para.h > linux-headers/asm-x86/unistd.h > linux-headers/asm-x86/unistd_32.h > linux-headers/asm-x86/unistd_64.h > linux-headers/asm-x86/unistd_x32.h > linux-headers/linux/kvm.h > linux-headers/linux/kvm_para.h > linux-headers/linux/psci.h > linux-headers/linux/userfaultfd.h > linux-headers/linux/vfio.h > linux-headers/linux/vhost.h > linux-headers/linux/virtio_config.h > linux-headers/linux/virtio_ring.h Same goes for linux-headers. We don't even touch those (beyond the massaging done by the import script). Maybe we could make get_maintainers.pl point at the maintainer for the import script for these headers? Or is there something more clever we could do?