ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Joerg Roedel <joro@8bytes.org>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Regression tracking
Date: Wed, 10 Aug 2016 00:55:22 +0200	[thread overview]
Message-ID: <1717921.V18WFsHkxD@vostro.rjw.lan> (raw)
In-Reply-To: <20160809223118.GG1437@8bytes.org>

On Wednesday, August 10, 2016 12:31:18 AM Joerg Roedel wrote:
> On Tue, Aug 09, 2016 at 09:02:22PM +0200, Thorsten Leemhuis wrote:
> > Yeah, definitely. One afaics important part that needs to be done in
> > this area: make bugzilla.kernel.org work better. At least some (or maybe
> > even quite a lot?) of the bugs reported there afaics seem to not get
> > proper attention from the right people. Due to that I'd assume some
> > testers will have come to conclusions like "testing for regressions and
> > bugs is not worth the trouble, as the kernel developers are not
> > interested in the bugs I file anyway".
> 
> 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.
> 
> So the right step here is to discuss how we want to get bugs reported
> and settle on a single way we tell the users and testers. From there it
> is much easier to get the reports dispatched to the right people.

I need to mention here that PM and ACPI regressions in bugzilla.kernel.org
are actually tracked by a team at Intel.  We track all of the PM and ACPI
bugs filed via the BZ, including regressions, and we're going to be doing
that.

Thanks,
Rafael

  reply	other threads:[~2016-08-09 22:50 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 [this message]
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
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=1717921.V18WFsHkxD@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --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