From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>, Takashi Iwai <tiwai@suse.de>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Regression tracking
Date: Mon, 1 Aug 2016 21:58:52 +0200 [thread overview]
Message-ID: <e3259012-57dd-19c1-d0af-262bd8e9b434@leemhuis.info> (raw)
In-Reply-To: <4b6ef14c-cea6-b51d-62db-ba3e708916ea@leemhuis.info>
On 27.07.2016 14:28, Thorsten Leemhuis wrote:
> On 26.07.2016 22:36, Rafael J. Wysocki wrote:
>>> On Tuesday, July 26, 2016 04:31:28 PM Takashi Iwai wrote:
> My rough plan after doing regression tracking for a few weeks now: Look
> a bit closer at patchwork and check if it can be adjusted to automate
> the boring parts of regression tracking. I have a mostly finished mail
> that has some more details on what got me thinking into that direction,
> but I'm on holiday till Friday and wanted to send it out once I'm home
> again.
FWIW, I posted my mail to LKML now:
http://lkml.kernel.org/r/e473a90f-7a20-52e8-0158-94f283638f34@leemhuis.info
Some of the thoughts and ideas mentioned there might be relevant for a
kernel summit discussion about regression tracking; let me know if there
is anything else I could do to help.
Ciao, Thorsten
next prev parent reply other threads:[~2016-08-01 19:58 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 [this message]
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
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=e3259012-57dd-19c1-d0af-262bd8e9b434@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=rjw@rjwysocki.net \
--cc=tiwai@suse.de \
/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