From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: "Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: OMAP baseline test results for v3.9-rc1
Date: Thu, 14 Mar 2013 17:16:56 +0530 [thread overview]
Message-ID: <5141B8B0.5050206@ti.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83EC281B4@DBDE01.ent.ti.com>
On Thursday 14 March 2013 04:59 PM, Hiremath, Vaibhav wrote:
>
>> -----Original Message-----
>> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
>> owner@vger.kernel.org] On Behalf Of Paul Walmsley
>> Sent: Tuesday, March 12, 2013 10:10 PM
>> To: linux-omap@vger.kernel.org
>> Cc: linux-arm-kernel@lists.infradead.org
>> Subject: OMAP baseline test results for v3.9-rc1
>>
>>
>> Here are some basic OMAP test results for Linux v3.9-rc1.
>> Logs and other details at:
>>
>> http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/
>>
>>
>> Test summary
>> ------------
>>
>> Build:
>> FAIL ( 4/16): am33xx_only, omap1_defconfig,
> This requires some cleanup in Makefile and Kconfig handling,
>
> Either you disable SMP support for non-SMP devices like AM33xx
>
> OR
>
> Fix the Makefile to resolve the build dependencies (may not be trivial)
>
This one... Better things is not to build the OMAP4 files for AM33XX only build.
Even if it is not trivial, its right way of fixing the issue.
Regards,
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.9-rc1
Date: Thu, 14 Mar 2013 17:16:56 +0530 [thread overview]
Message-ID: <5141B8B0.5050206@ti.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83EC281B4@DBDE01.ent.ti.com>
On Thursday 14 March 2013 04:59 PM, Hiremath, Vaibhav wrote:
>
>> -----Original Message-----
>> From: linux-omap-owner at vger.kernel.org [mailto:linux-omap-
>> owner at vger.kernel.org] On Behalf Of Paul Walmsley
>> Sent: Tuesday, March 12, 2013 10:10 PM
>> To: linux-omap at vger.kernel.org
>> Cc: linux-arm-kernel at lists.infradead.org
>> Subject: OMAP baseline test results for v3.9-rc1
>>
>>
>> Here are some basic OMAP test results for Linux v3.9-rc1.
>> Logs and other details at:
>>
>> http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/
>>
>>
>> Test summary
>> ------------
>>
>> Build:
>> FAIL ( 4/16): am33xx_only, omap1_defconfig,
> This requires some cleanup in Makefile and Kconfig handling,
>
> Either you disable SMP support for non-SMP devices like AM33xx
>
> OR
>
> Fix the Makefile to resolve the build dependencies (may not be trivial)
>
This one... Better things is not to build the OMAP4 files for AM33XX only build.
Even if it is not trivial, its right way of fixing the issue.
Regards,
Santosh
next prev parent reply other threads:[~2013-03-14 11:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 16:40 OMAP baseline test results for v3.9-rc1 Paul Walmsley
2013-03-12 16:40 ` Paul Walmsley
2013-03-12 16:51 ` Paul Walmsley
2013-03-12 16:51 ` Paul Walmsley
2013-03-12 19:00 ` Aaro Koskinen
2013-03-12 19:00 ` Aaro Koskinen
2013-03-13 10:20 ` Paul Walmsley
2013-03-13 10:20 ` Paul Walmsley
2013-03-14 16:14 ` Paul Walmsley
2013-03-14 16:14 ` Paul Walmsley
2013-03-13 7:34 ` Igor Grinberg
2013-03-13 7:34 ` Igor Grinberg
2013-03-13 10:22 ` Paul Walmsley
2013-03-13 10:22 ` Paul Walmsley
2013-03-14 11:29 ` Hiremath, Vaibhav
2013-03-14 11:29 ` Hiremath, Vaibhav
2013-03-14 11:46 ` Santosh Shilimkar [this message]
2013-03-14 11:46 ` Santosh Shilimkar
2013-03-26 18:44 ` Paul Walmsley
2013-03-26 18:44 ` Paul Walmsley
2013-03-19 5:47 ` Paul Walmsley
2013-03-19 5:47 ` 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=5141B8B0.5050206@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=hvaibhav@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.