From: Gerd Hoffmann <kraxel@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Thomas Huth <thuth@redhat.com>, David Airlie <airlied@redhat.com>,
dri-devel@lists.freedesktop.org, qemu-devel@nongnu.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH] drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl, virtio-gpu)
Date: Wed, 23 Nov 2016 09:06:36 +0100 [thread overview]
Message-ID: <1479888396.16465.5.camel@redhat.com> (raw)
In-Reply-To: <e794391a-1431-0914-e968-29660f1830a6@redhat.com>
Hi,
> >>>>>> +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 ?
> 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@lists.linux-foundation.org would be a better choice
than qemu-devel ...
cheers,
Gerd
WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
open list <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org, qemu-devel@nongnu.org,
David Airlie <airlied@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl, virtio-gpu)
Date: Wed, 23 Nov 2016 09:06:36 +0100 [thread overview]
Message-ID: <1479888396.16465.5.camel@redhat.com> (raw)
In-Reply-To: <e794391a-1431-0914-e968-29660f1830a6@redhat.com>
Hi,
> >>>>>> +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 ?
> 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@lists.linux-foundation.org would be a better choice
than qemu-devel ...
cheers,
Gerd
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-11-23 8:06 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 ` Gerd Hoffmann
2016-11-22 9:58 ` [Qemu-devel] " Gerd Hoffmann
2016-11-22 10:50 ` Thomas Huth
2016-11-22 18:54 ` Eric Blake
2016-11-22 18:54 ` Eric Blake
2016-11-22 19:41 ` Paolo Bonzini
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 [this message]
2016-11-23 8:06 ` Gerd Hoffmann
2016-11-23 8:13 ` Thomas Huth
2016-11-23 8:13 ` 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=1479888396.16465.5.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eblake@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--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.