From: Joerg Roedel <joro@8bytes.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Regression tracking
Date: Wed, 10 Aug 2016 17:01:44 +0200 [thread overview]
Message-ID: <20160810150144.GH1437@8bytes.org> (raw)
In-Reply-To: <87h9asx23l.fsf@intel.com>
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.
Joerg
next prev parent reply other threads:[~2016-08-10 15:01 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 [this message]
2016-08-10 16:19 ` Daniel Vetter
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=20160810150144.GH1437@8bytes.org \
--to=joro@8bytes.org \
--cc=jani.nikula@intel.com \
--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