linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: trini@ti.com (Tom Rini)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.10-rc6
Date: Wed, 26 Jun 2013 16:02:02 -0400	[thread overview]
Message-ID: <51CB48BA.7020401@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306261750210.6135@utopia.booyaka.com>

On 06/26/2013 01:58 PM, Paul Walmsley wrote:
> On Wed, 26 Jun 2013, Tom Rini wrote:
> 
>> OK, is there a reason to not be using omap2plus_defconfig?  My pass/fail
>> here is based on that config and enabling, or not, dtb append.  Seems
>> like it would be one less thing to maintain on your end and it would be
>> on TIs end (roughly speaking) to make sure our platforms that ought to
>> be working upstream have what they need enabled in the defconfig(s) in
>> question.
> 
> That would be convenient for me, but part of the goal is to verify that a 
> Kconfig that deselects all OMAPs other than AM33xx continues to work.
> 
> So the build process for am33xx_only here goes something like:
> 
> 1. Start with omap2plus_defconfig
> 
> 2. Turn off support for everything other than AM33xx in the SoC target 
> selection menus
> 
> 3. Turn on the appended DTB and compat ATAGs options
> 
> You might consider adding something like this to your pass/fail tests.

Adding more and different build+boot tests is on the list.  I guess you
could automate this with a fraagment of everything am33xx must have to
boot+root and alldefconfig for the rest?

-- 
Tom

  reply	other threads:[~2013-06-26 20:02 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17  5:23 OMAP baseline test results for v3.10-rc6 Paul Walmsley
2013-06-25 16:02 ` Felipe Balbi
2013-06-25 18:20   ` Paul Walmsley
2013-06-25 19:34     ` Tom Rini
2013-06-25 19:57       ` Kevin Hilman
2013-06-25 20:22         ` Tom Rini
2013-06-26  9:15           ` Russell King - ARM Linux
2013-06-26 11:27             ` Tom Rini
2013-06-26  4:53         ` Hiremath, Vaibhav
2013-06-26 13:22           ` Rajendra Nayak
2013-06-26 13:26             ` Tom Rini
2013-06-26 17:28               ` Paul Walmsley
2013-06-26 17:45                 ` Tom Rini
2013-06-26 17:58                   ` Paul Walmsley
2013-06-26 20:02                     ` Tom Rini [this message]
2013-06-26 23:57                       ` Kevin Hilman
2013-06-26 17:26             ` Paul Walmsley
2013-06-27  4:17               ` Lokesh Vutla
2013-06-28 18:45                 ` Paul Walmsley
2013-07-01  2:15                   ` Paul Walmsley
2013-07-02  4:29                     ` Hiremath, Vaibhav
2013-07-02 14:15                       ` Nishanth Menon
2013-07-03 19:51                         ` Paul Walmsley
2013-07-04 18:12                           ` Paul Walmsley
2013-07-05  5:48                             ` Rajendra Nayak
2013-07-05 14:14                               ` Tom Rini
2013-07-05 15:44                               ` Paul Walmsley
2013-06-26 20:56           ` Kevin Hilman
2013-06-26 17:19       ` Paul Walmsley
2013-06-26 20:16         ` Tom Rini
2013-07-29  8:29           ` Paul Walmsley
2013-07-29 12:29             ` Tom Rini
2013-07-30 20:23               ` Paul Walmsley
2013-07-30 20:28                 ` Nishanth Menon
2013-06-25 20:39     ` Felipe Balbi
2013-06-26  4:57     ` Hiremath, Vaibhav
2013-06-26 16:51       ` Paul Walmsley
2013-06-26 17:41         ` Paul Walmsley
2013-06-26  9:21     ` Lokesh Vutla
2013-06-26 17:36       ` Paul Walmsley

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=51CB48BA.7020401@ti.com \
    --to=trini@ti.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).