From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Borislav Petkov <bp@alien8.de>
Cc: Takashi Iwai <tiwai@suse.de>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: 4.7-rc3: Reported regressions from 4.7
Date: Mon, 13 Jun 2016 15:53:20 +0200 [thread overview]
Message-ID: <2854772.QvWZVI5fde@vostro.rjw.lan> (raw)
In-Reply-To: <20160613133648.GB3717@pd.tnic>
On Monday, June 13, 2016 03:36:48 PM Borislav Petkov wrote:
> On Mon, Jun 13, 2016 at 01:53:34PM +0200, Takashi Iwai wrote:
> > Well, Rafael created a bugzilla entry for tracking in the past, so
> > using bugzilla as tracking tool works in general. It doesn't mean
> > it's the best option, of course, though.
>
> So I don't care whether it is buzgilla or some other central place which
> can show you all regressions at once and Thorsten can edit it quickly so
> that interested parties can get the latest status of a regression and
> not waste time with stale emails.
I used kernel BZ entries for two reasons.
First, some of the bugs were in the kernel BZ already, so they could be added
to the tracked list very easily when it was in BZ itself. Second, some people
actually used BZ entries created by me to work on the bugs going forward (for
storing logs, acpidumps and similar).
Thanks,
Rafael
next prev parent reply other threads:[~2016-06-13 13:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 17:22 Thorsten Leemhuis
2016-06-13 8:07 ` Borislav Petkov
2016-06-13 8:20 ` Takashi Iwai
2016-06-13 10:59 ` Thorsten Leemhuis
2016-06-13 11:02 ` Borislav Petkov
2016-06-13 11:53 ` Takashi Iwai
2016-06-13 13:36 ` Borislav Petkov
2016-06-13 13:53 ` Rafael J. Wysocki [this message]
2016-06-13 13:53 ` Borislav Petkov
2016-06-13 20:35 ` Rafael J. Wysocki
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=2854772.QvWZVI5fde@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®