Re: [Qemu-devel] MAINTAINERS leaves too many files uncovered

[Cornelia Huck]

On Tue, 30 Aug 2016 13:31:12 +0200
Markus Armbruster <address@hidden> 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?