All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>, Thomas Huth <thuth@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	David Airlie <airlied@redhat.com>,
	dri-devel@lists.freedesktop.org, qemu-devel@nongnu.org
Cc: open list <linux-kernel@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH] drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl, virtio-gpu)
Date: Tue, 22 Nov 2016 20:41:27 +0100	[thread overview]
Message-ID: <ea9b16fb-d0e9-3c97-e36c-e08419b37664@redhat.com> (raw)
In-Reply-To: <8871cadb-3edf-5a3f-2da5-8981c12b79a0@redhat.com>



On 22/11/2016 19:54, Eric Blake wrote:
>>> >>  DRM DRIVER FOR BOCHS VIRTUAL GPU
>>> >>  M:	Gerd Hoffmann <kraxel@redhat.com>
>>> >> -S:	Odd Fixes
>>> >> +L:	qemu-devel@nongnu.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@nongnu.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
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>, Thomas Huth <thuth@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	David Airlie <airlied@redhat.com>,
	dri-devel@lists.freedesktop.org, qemu-devel@nongnu.org
Cc: open list <linux-kernel@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH] drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl, virtio-gpu)
Date: Tue, 22 Nov 2016 20:41:27 +0100	[thread overview]
Message-ID: <ea9b16fb-d0e9-3c97-e36c-e08419b37664@redhat.com> (raw)
In-Reply-To: <8871cadb-3edf-5a3f-2da5-8981c12b79a0@redhat.com>



On 22/11/2016 19:54, Eric Blake wrote:
>>> >>  DRM DRIVER FOR BOCHS VIRTUAL GPU
>>> >>  M:	Gerd Hoffmann <kraxel@redhat.com>
>>> >> -S:	Odd Fixes
>>> >> +L:	qemu-devel@nongnu.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@nongnu.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

  reply	other threads:[~2016-11-22 19:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22  9:58 [PATCH] drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl, virtio-gpu) Gerd Hoffmann
2016-11-22  9:58 ` [Qemu-devel] " Gerd Hoffmann
2016-11-22  9:58 ` Gerd Hoffmann
2016-11-22 10:50 ` [Qemu-devel] " Thomas Huth
2016-11-22 18:54   ` Eric Blake
2016-11-22 18:54     ` Eric Blake
2016-11-22 19:41     ` Paolo Bonzini [this message]
2016-11-22 19:41       ` Paolo Bonzini
2016-11-22 20:47       ` Eric Blake
2016-11-22 20:47         ` Eric Blake
2016-11-23  8:06         ` Gerd Hoffmann
2016-11-23  8:06           ` Gerd Hoffmann
2016-11-23  8:13           ` Thomas Huth
2016-11-23  8:13             ` [Qemu-devel] " Thomas Huth

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=ea9b16fb-d0e9-3c97-e36c-e08419b37664@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eblake@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.