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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ea9b16fb-d0e9-3c97-e36c-e08419b37664@redhat.com>
Date:   Tue, 22 Nov 2016 20:41:27 +0100
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Eric Blake <eblake@...hat.com>, Thomas Huth <thuth@...hat.com>,
        Gerd Hoffmann <kraxel@...hat.com>,
        David Airlie <airlied@...hat.com>,
        dri-devel@...ts.freedesktop.org, qemu-devel@...gnu.org
Cc:     open list <linux-kernel@...r.kernel.org>
Subject: Re: [Qemu-devel] [PATCH] drm: update MAINTAINERS for qemu drivers
 (bochs, cirrus, qxl, virtio-gpu)



On 22/11/2016 19:54, Eric Blake wrote:
>>> >>  DRM DRIVER FOR BOCHS VIRTUAL GPU
>>> >>  M:	Gerd Hoffmann <kraxel@...hat.com>
>>> >> -S:	Odd Fixes
>>> >> +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 ?
> In practice, ALL patches should already be going to qemu-devel, even if
> they are ALSO going to some other list.  For example, qemu-block and
> qemu-trivial are definitely cases where we have separate lists, but
> where posters are reminded to include qemu-devel in cc if they want a
> patch applied.

The difference is that these would be kernel patches.

Paolo

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ