From: Jani Nikula <jani.nikula@intel.com>
To: Joerg Roedel <joro@8bytes.org>,
Thorsten Leemhuis <regressions@leemhuis.info>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Regression tracking
Date: Wed, 10 Aug 2016 15:03:42 +0300 [thread overview]
Message-ID: <87h9asx23l.fsf@intel.com> (raw)
In-Reply-To: <20160809223118.GG1437@8bytes.org>
On Wed, 10 Aug 2016, Joerg Roedel <joro@8bytes.org> wrote:
> In my case, I am only looking into the kernel.org bugzilla if someone
> pings me about it. Usually I get the upstream bug reports via email. And
> this is part of the problem, that we have multiple ways that we teach
> users how to report bugs/regressions. That really increases the effort
> needed for you to compile the regression list and keep track of
> everything in there.
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/.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-08-10 12:03 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 [this message]
2016-08-10 15:01 ` Joerg Roedel
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=87h9asx23l.fsf@intel.com \
--to=jani.nikula@intel.com \
--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