From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.17-rc7
Date: Thu, 2 Oct 2014 09:17:15 -0700 [thread overview]
Message-ID: <20141002161714.GI3122@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1410021447590.31530@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [141002 08:11]:
>
> Maybe you have some ideas for how this can be communicated better in the
> test results? One thing that would probably help is if the board was
> renamed to "3730es10beaglexm" or something like that. Also maybe
> mentioning the fact that the test is only needed due to errata, like:
>
> -----------
> PM: chip off (except CORE, due to errata) via dynamic idle:
> Pass ( 1/ 1): 3730es10beaglexm
> -----------
Oh OK, yeah I did not read the actual test :) The above description
makes it clear at least for me.
Regards,
Tony
prev parent reply other threads:[~2014-10-02 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 17:13 OMAP baseline test results for v3.17-rc7 Paul Walmsley
2014-09-29 17:20 ` Tony Lindgren
2014-10-02 15:10 ` Paul Walmsley
2014-10-02 16:17 ` Tony Lindgren [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=20141002161714.GI3122@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).