| Message ID | 1479808693-30234-1-git-send-email-kraxel@redhat.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On 22.11.2016 10:58, Gerd Hoffmann wrote: > Changes: > * add myself as maintainer, so patches land in my inbox. > * add qemu-devel mailing list. > * add drm-qemu git repo. > * flip bochs and qxl status to "Maintained". > > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com> > --- > MAINTAINERS | 14 ++++++++++++-- > 1 file changed, 12 insertions(+), 2 deletions(-) > > diff --git a/MAINTAINERS b/MAINTAINERS > index ad9b965..84dc747 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -4027,11 +4027,16 @@ F: drivers/gpu/drm/ast/ > > 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 ? Thomas
On 11/22/2016 04:50 AM, Thomas Huth wrote: > On 22.11.2016 10:58, Gerd Hoffmann wrote: >> Changes: >> * add myself as maintainer, so patches land in my inbox. >> * add qemu-devel mailing list. >> * add drm-qemu git repo. >> * flip bochs and qxl status to "Maintained". >> >> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com> >> --- >> MAINTAINERS | 14 ++++++++++++-- >> 1 file changed, 12 insertions(+), 2 deletions(-) >> >> diff --git a/MAINTAINERS b/MAINTAINERS >> index ad9b965..84dc747 100644 >> --- a/MAINTAINERS >> +++ b/MAINTAINERS >> @@ -4027,11 +4027,16 @@ F: drivers/gpu/drm/ast/ >> >> 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.
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
On 11/22/2016 01:41 PM, Paolo Bonzini wrote: > > > 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. Ah, indeed. I missed the distinction of 'all _qemu_ patches' are already going to the qemu list, but this is about non-qemu patches. I guess I was thrown off because I first read this message as cross-posted onto the qemu lists, rather than its primary audience of the kernel list. But it goes to show that when more than one non-overlapping list is cc'd on an individual patch, it gets harder to tell which list the patch is meant for, vs. which other lists are just getting it out of courtesy. 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.
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
On 23.11.2016 09:06, Gerd Hoffmann wrote: > 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 ... Yes, I agree, that sounds like a better fit. You might even get the attention from other people there who are working on virtualization solutions other than QEMU. Thomas
diff --git a/MAINTAINERS b/MAINTAINERS index ad9b965..84dc747 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -4027,11 +4027,16 @@ F: drivers/gpu/drm/ast/ DRM DRIVER FOR BOCHS VIRTUAL GPU M: Gerd Hoffmann <kraxel@redhat.com> -S: Odd Fixes +L: qemu-devel@nongnu.org +T: git git://git.kraxel.org/linux drm-qemu +S: Maintained F: drivers/gpu/drm/bochs/ DRM DRIVER FOR QEMU'S CIRRUS DEVICE M: Dave Airlie <airlied@redhat.com> +M: Gerd Hoffmann <kraxel@redhat.com> +L: qemu-devel@nongnu.org +T: git git://git.kraxel.org/linux drm-qemu S: Odd Fixes F: drivers/gpu/drm/cirrus/ @@ -4204,7 +4209,10 @@ F: Documentation/devicetree/bindings/display/renesas,du.txt DRM DRIVER FOR QXL VIRTUAL GPU M: Dave Airlie <airlied@redhat.com> -S: Odd Fixes +M: Gerd Hoffmann <kraxel@redhat.com> +L: qemu-devel@nongnu.org +T: git git://git.kraxel.org/linux drm-qemu +S: Maintained F: drivers/gpu/drm/qxl/ F: include/uapi/drm/qxl_drm.h @@ -12825,6 +12833,8 @@ M: David Airlie <airlied@linux.ie> M: Gerd Hoffmann <kraxel@redhat.com> L: dri-devel@lists.freedesktop.org L: virtualization@lists.linux-foundation.org +L: qemu-devel@nongnu.org +T: git git://git.kraxel.org/linux drm-qemu S: Maintained F: drivers/gpu/drm/virtio/ F: include/uapi/linux/virtio_gpu.h
Changes: * add myself as maintainer, so patches land in my inbox. * add qemu-devel mailing list. * add drm-qemu git repo. * flip bochs and qxl status to "Maintained". Signed-off-by: Gerd Hoffmann <kraxel@redhat.com> --- MAINTAINERS | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-)