dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
	Daniel Vetter <daniel.vetter@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] MAINTAINERS: Add an entry for the vboxvideo driver
Date: Wed, 13 Mar 2019 10:53:26 +0200	[thread overview]
Message-ID: <87va0ni29l.fsf@intel.com> (raw)
In-Reply-To: <69cd4863-0aa2-2647-61a7-c11ad7757f6a@redhat.com>

On Wed, 13 Mar 2019, Hans de Goede <hdegoede@redhat.com> wrote:
> Hi,
>
> On 3/13/19 9:26 AM, Jani Nikula wrote:
>> On Mon, 11 Mar 2019, Hans de Goede <hdegoede@redhat.com> wrote:
>>> Add a MAINTAINERS entry for the vboxvideo driver, now that it has been
>>> moved out of staging.
>>>
>>> Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>>> ---
>>>   MAINTAINERS | 7 +++++++
>>>   1 file changed, 7 insertions(+)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 81d484891b53..36577f5db872 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -4932,6 +4932,13 @@ S:	Odd Fixes
>>>   F:	drivers/gpu/drm/udl/
>>>   T:	git git://anongit.freedesktop.org/drm/drm-misc
>>>   
>>> +DRM DRIVER FOR VIRTUALBOX VIRTUAL GPU
>>> +M:	Hans de Goede <hdegoede@redhat.com>
>>> +L:	dri-devel@lists.freedesktop.org
>>> +S:	Maintained
>>> +F:	drivers/gpu/drm/vboxvideo/
>>> +T:	git git://anongit.freedesktop.org/drm/drm-misc
>> 
>> Please consider adding B: and C: entries, and perhaps W: if applicable.
>
> Should the B: point to bugzilla.kernel.org or bugzilla.freedesktop.org?

This is perhaps a point of contention. drm/i915 has completely switched
to fdo bugzilla, and we close any kernel.org bugs on sight with
instructions to file the bug at fdo. IMHO all of drm would benefit from
switching over to fdo bugzilla (or gitlab issues going forward).

> also most B: entries just point to a bugzilla, without
> specifying which component to use, which is not really helpful.
> The B: for i915 seems good, but setting up a similar webpage for
> each driver seems like a bad idea.

The i915 page needs an overhaul. But you could also use something like:

https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel

> I think that we may need some
> generic howto report drm driver bugs page somewhere ?
>
> As for the C: I am more or less the main point of contact and I'm
> more often not on irc then that I'm on irc since I find that irc
> distracts me too much. So I think it is better to not have a C:
> for the vboxvideo driver.

I think that's fine.

Also, I have nothing against merging the patch at hand as-is, and
updating the rest later.


BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2019-03-13  8:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11 16:35 [PATCH] MAINTAINERS: Add an entry for the vboxvideo driver Hans de Goede
2019-03-11 20:49 ` Alex Deucher
2019-03-13  8:26 ` Jani Nikula
2019-03-13  8:30   ` Daniel Vetter
2019-03-13  8:47     ` Jani Nikula
2019-03-13  8:33   ` Hans de Goede
2019-03-13  8:53     ` Jani Nikula [this message]

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=87va0ni29l.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hdegoede@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 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).