From: "Mark Brown" <broonie@kernel.org>
To: kernelci@groups.io
Cc: Mark Brown <broonie@kernal.org>, Kevin Hilman <khilman@baylibre.com>
Subject: Re: [kernelci] next/master boot bisection: next-20181210 on meson-gxl-s905x-libretech-cc
Date: Tue, 11 Dec 2018 12:07:20 +0000 [thread overview]
Message-ID: <20181211120720.GC6686@sirena.org.uk> (raw)
In-Reply-To: <fff93168-d5b1-9997-c562-41e26461ba7a@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
On Tue, Dec 11, 2018 at 08:58:28AM +0000, Guillaume Tucker wrote:
> On 11/12/2018 00:53, Mark Brown wrote:
> > It does say in the subject that it's a boot - perhaps we should put
> > something in the body as well? It doesn't actually get mentioned there.
> Parameters:
> Tree: next
> URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> Branch: master
> Target: meson-gxl-s905x-libretech-cc
> Lab: lab-baylibre
> Config: defconfig+CONFIG_CPU_BIG_ENDIAN=y
> Plan: boot
> The "Plan" parameter here says it's a "boot".
> Maybe we could have a link to a wiki page explaining what our
> test plans are, in case the recipients aren't familiar with any
> test plan. Also, maybe "Test Suite" would be easier to
> understand than "Plan".
I think the problem is more that it's towards the bottom of a table of
stuff and people aren't going to get that far into reading the mail in
the first place. How about changing the "Bisection result..." line to
be "Boot bisection result..." instead?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-12-11 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5c0ef32c.1c69fb81.72744.44d8@mx.google.com>
2018-12-10 23:38 ` next/master boot bisection: next-20181210 on meson-gxl-s905x-libretech-cc Kevin Hilman
2018-12-10 23:49 ` Guillaume Tucker
2018-12-11 21:47 ` Kevin Hilman
2018-12-12 12:50 ` Guillaume Tucker
2018-12-11 0:53 ` [kernelci] " Mark Brown
2018-12-11 8:58 ` Guillaume Tucker
2018-12-11 12:07 ` Mark Brown [this message]
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=20181211120720.GC6686@sirena.org.uk \
--to=broonie@kernel.org \
--cc=broonie@kernal.org \
--cc=kernelci@groups.io \
--cc=khilman@baylibre.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