mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Borislav Petkov <bp@alien8.de>
Cc: 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 10:20:25 +0200	[thread overview]
Message-ID: <s5hlh29zeie.wl-tiwai@suse.de> (raw)
In-Reply-To: <20160613080748.GA19292@pd.tnic>

On Mon, 13 Jun 2016 10:07:48 +0200,
Borislav Petkov wrote:
> 
> Hey thl,
> 
> On Sun, Jun 12, 2016 at 07:22:17PM +0200, Thorsten Leemhuis wrote:
> > Hi! As announced last week in http://article.gmane.org/gmane.linux.kernel/2233992 
> > I'll try to write regression reports for 4.7. Find the first one below.
> 
> looks good, thanks for volunteering.

Indeed, it's really appreciated!

> So I'm wondering, would it make more sense to have a web page somewhere
> which carries all those and gets updated when status ot any tracked
> regression changes?
> 
> So that people can look at it and get the latest on the regressions
> front instead of trying to find a possibly outdated mail to lkml?

Another idea is to use "Keywords" or "Tags" field in each bugzilla
entry.  Then you can let bugzilla showing up the all such entries.


Takashi

  reply	other threads:[~2016-06-13  8:20 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 [this message]
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
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=s5hlh29zeie.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --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®