ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Joerg Roedel <joro@8bytes.org>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Regression tracking
Date: Wed, 10 Aug 2016 18:19:43 +0200	[thread overview]
Message-ID: <CAKMK7uGtyGoGDzLcgw8GDwhVkiCanHkigSfy869a5U4LJBLN2g@mail.gmail.com> (raw)
In-Reply-To: <20160810150144.GH1437@8bytes.org>

On Wed, Aug 10, 2016 at 5:01 PM, Joerg Roedel <joro@8bytes.org> wrote:
> On Wed, Aug 10, 2016 at 03:03:42PM +0300, Jani Nikula wrote:
>> How about adding an entry, say "B:", to MAINTAINERS to let each
>> subsystem/driver specify the preferred method of reporting bugs? For
>> example, most drivers/gpu/drm bugs would get more attention at
>> https://bugs.freedesktop.org/ than https://bugzilla.kernel.org/.
>
> I thought about that too, it might make sense if we can't agree on
> anything better. In the end it is more hassle for the users and requires
> more knowledge on their side. They have to know at least in which part of
> the kernel the problem occured and then look that part up in the
> MAINTAINERS file to find out how to report the bug. There are probably
> quite a few users who give up somewhere on that path.

We already have this trouble on the gfx side, just worse: Users
generally have no idea which one of kernel driver, X driver, mesa/gl,
libva/video or whatever exactly blew up. Which is why we're
redirecting everyone to bugs.freedesktop.org, there we can at elast
reassign between the different parts.

Of course that then means we can't easily reassing to other kernel
components, but that seems to happen far less often (for us).

Anyway, +1 from me for B: in MAINTAINERS to make it at least possible
for users to figure out where to file a bug. Default would be mailo:
<mailing list from same maintainer entry>.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2016-08-10 16:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 14:31 Takashi Iwai
2016-07-26 20:36 ` Rafael J. Wysocki
2016-07-27 12:28   ` Thorsten Leemhuis
2016-08-01 19:58     ` Thorsten Leemhuis
2016-08-09  9:40     ` Joerg Roedel
2016-08-09 19:02       ` Thorsten Leemhuis
2016-08-09 20:21         ` Takashi Iwai
2016-08-09 22:31         ` Joerg Roedel
2016-08-09 22:55           ` Rafael J. Wysocki
2016-08-09 23:20           ` James Bottomley
2016-08-10 15:11             ` Joerg Roedel
2016-08-10 12:03           ` Jani Nikula
2016-08-10 15:01             ` Joerg Roedel
2016-08-10 16:19               ` Daniel Vetter [this message]
2016-08-10 16:47         ` Laura Abbott

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=CAKMK7uGtyGoGDzLcgw8GDwhVkiCanHkigSfy869a5U4LJBLN2g@mail.gmail.com \
    --to=daniel.vetter@ffwll.ch \
    --cc=joro@8bytes.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=regressions@leemhuis.info \
    /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