From: Jon Hunter <jon-hunter@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: OMAP baseline test results for v3.7-rc2
Date: Mon, 22 Oct 2012 13:50:23 -0500 [thread overview]
Message-ID: <5085956F.8000405@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1210221835520.13464@utopia.booyaka.com>
On 10/22/2012 01:36 PM, Paul Walmsley wrote:
> On Mon, 22 Oct 2012, Paul Walmsley wrote:
>
>> On Mon, 22 Oct 2012, Jon Hunter wrote:
>>
>>> and toolchain used for any failures.
>>
>> This would indeed be useful and will try to figure out a good way to add
>> that information.
>
> Just realized that some of this appears in the beginning of the bootlogs:
>
> [ 0.000000] Linux version 3.7.0-rc2-00331-g6f0c058 (paul@nozomi) (gcc
> version 4.5.1 (Sourcery G++ Lite 2010.09-50) ) #1 SMP Sat Oct 20 14:04:56
> MDT 2012
>
> Not the easiest information to find, but maybe it serves your needs?
Yes, it does. The boot log has all the info we need :-)
Cheers
Jon
next prev parent reply other threads:[~2012-10-22 18:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 21:26 OMAP baseline test results for v3.7-rc2 Paul Walmsley
2012-10-21 17:06 ` Paul Walmsley
2012-10-22 16:10 ` Jon Hunter
2012-10-22 17:17 ` Paul Walmsley
2012-10-22 17:18 ` Paul Walmsley
2012-10-22 16:28 ` Jon Hunter
2012-10-22 16:38 ` Tony Lindgren
2012-10-23 19:34 ` Paul Walmsley
2012-10-22 18:35 ` Paul Walmsley
2012-10-22 18:36 ` Paul Walmsley
2012-10-22 18:50 ` Jon Hunter [this message]
2012-10-22 18:48 ` Jon Hunter
2012-10-23 1:53 ` Matt Porter
2012-10-23 3:15 ` Paul Walmsley
2012-10-23 4:57 ` Paul Walmsley
2012-10-23 12:24 ` Matt Porter
2012-10-23 13:11 ` Matt Porter
2012-10-23 21:03 ` Kevin Hilman
2012-10-23 21:11 ` Matt Porter
2012-10-25 14:14 ` Kevin Hilman
2012-10-23 1:04 ` Kevin Hilman
2012-10-23 18:19 ` Kevin Hilman
2012-10-24 9:01 ` Igor Grinberg
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=5085956F.8000405@ti.com \
--to=jon-hunter@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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).