linux-kernel - Re: [Qemu-devel] [PATCH] drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl, virtio-gpu)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <772c480f-86c5-3162-256c-45ee9c0cc9ea@redhat.com>
Date:   Wed, 23 Nov 2016 09:13:49 +0100
From:   Thomas Huth <thuth@...hat.com>
To:     Gerd Hoffmann <kraxel@...hat.com>, Eric Blake <eblake@...hat.com>
Cc:     Paolo Bonzini <pbonzini@...hat.com>,
        David Airlie <airlied@...hat.com>,
        dri-devel@...ts.freedesktop.org, qemu-devel@...gnu.org,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [Qemu-devel] [PATCH] drm: update MAINTAINERS for qemu drivers
 (bochs, cirrus, qxl, virtio-gpu)

On 23.11.2016 09:06, Gerd Hoffmann wrote:
>   Hi,
> 
>>>>>>>> +L:	qemu-devel@...gnu.org
>>>>>>
>>>>>> qemu-devel list already has very high traffic - not sure whether it
>>>>>> makes much sense to route even more additional patches here. Maybe
>>>>>> rather create a separate mailing list like qemu-graphics@...gnu.org ?
> 
>> So you've just managed to convince me that including qemu-devel on every
>> driver patch, when qemu.git will not be modified, may indeed be
>> overkill; when compared to the option of just creating a new dedicated
>> list for the subset of kernel patches related to qemu drivers.
> 
> Well, that isn't my intention.  I want the kernel patches for qemu
> graphics being more visible for developers working on the host (device
> emulation) side.  A separate list just for those patches is quite the
> contrary ...
> 
> Maybe virtualization@...ts.linux-foundation.org would be a better choice
> than qemu-devel ...

Yes, I agree, that sounds like a better fit. You might even get the
attention from other people there who are working on virtualization
solutions other than QEMU.

 Thomas