From: Mark Brown <broonie@kernel.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Tony Lindgren <tony@atomide.com>, Stephen Boyd <sboyd@kernel.org>,
"kernelci.org bot" <bot@kernelci.org>,
Jeffrey Hugo <jhugo@codeaurora.org>,
enric.balletbo@collabora.com, khilman@baylibre.com,
matthew.hart@linaro.org, mgalka@collabora.com,
tomeu.vizoso@collabora.com,
Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: clk/clk-next boot bisection: v5.1-rc1-142-ga55b079c961b on panda
Date: Thu, 25 Apr 2019 19:17:36 +0100 [thread overview]
Message-ID: <20190425181736.GD23183@sirena.org.uk> (raw)
In-Reply-To: <9d076ce7-ce9b-07d9-21c7-e3e2eddf2fdb@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
On Thu, Apr 25, 2019 at 06:44:16PM +0100, Guillaume Tucker wrote:
> Also there aren't that many bisections, maybe a couple per month.
> I think we could cc the KernelCI reports mailing list, or maybe
> have a new list, for people who want to receive all the bisection
> reports. There should be more as we keep adding trees and
> especially when we start bisecting test suite results, not just
> boots.
This is the sort of thing that tends to go in phases as subsystems get
worked on IME - if something is getting disruptive work done on it you
can get a lot of issues for a while. You'd also see a lot more reports
if all boards got reported.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-04-25 18:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 0:16 clk/clk-next boot bisection: v5.1-rc1-142-ga55b079c961b on panda kernelci.org bot
2019-04-23 1:06 ` Stephen Boyd
2019-04-23 11:54 ` Geert Uytterhoeven
2019-04-23 14:40 ` Tony Lindgren
2019-04-25 17:28 ` Mark Brown
2019-04-25 17:44 ` Guillaume Tucker
2019-04-25 18:17 ` Mark Brown [this message]
2019-04-25 19:28 ` Tony Lindgren
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=20190425181736.GD23183@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bot@kernelci.org \
--cc=enric.balletbo@collabora.com \
--cc=guillaume.tucker@collabora.com \
--cc=jhugo@codeaurora.org \
--cc=khilman@baylibre.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.hart@linaro.org \
--cc=mgalka@collabora.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=tomeu.vizoso@collabora.com \
--cc=tony@atomide.com \
/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;
as well as URLs for NNTP newsgroup(s).