qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: [Qemu-devel] RfC: MAINTAINERS update for qemu drm drivers.
Date: Mon, 21 Nov 2016 19:24:34 +0100	[thread overview]
Message-ID: <1479752674.9742.54.camel@redhat.com> (raw)

  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

             reply	other threads:[~2016-11-21 18:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21 18:24 Gerd Hoffmann [this message]
2016-11-21 19:05 ` [Qemu-devel] RfC: MAINTAINERS update for qemu drm drivers Daniel Vetter
2016-11-21 19:22   ` Gerd Hoffmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1479752674.9742.54.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).