From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49514) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c8tGk-0004DC-AQ for qemu-devel@nongnu.org; Mon, 21 Nov 2016 13:24:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c8tGf-0001AN-F0 for qemu-devel@nongnu.org; Mon, 21 Nov 2016 13:24:42 -0500 Received: from mx1.redhat.com ([209.132.183.28]:52970) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c8tGf-00018q-9s for qemu-devel@nongnu.org; Mon, 21 Nov 2016 13:24:37 -0500 Message-ID: <1479752674.9742.54.camel@redhat.com> From: Gerd Hoffmann Date: Mon, 21 Nov 2016 19:24:34 +0100 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 Subject: [Qemu-devel] RfC: MAINTAINERS update for qemu drm drivers. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel Cc: dri-devel Hi, I'm busy updating the MAINTAINERS file for the linux kernel, making sure I'm listed for all qemu drm drivers (cirrus, bochs, qxl, virtio), so patches land in my inbox. While being at it: I'm wondering whenever it makes sense to also include the qemu-devel list there. I think it would be useful, so qemu developers can see what is going on without being subscribed to dri-devel. Comments? thanks, Gerd