From: Tero Kristo <t-kristo@ti.com>
To: balbi@ti.com
Cc: tony@atomide.com, linux-omap@vger.kernel.org,
mturquette@linaro.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] ARM: DRA7XX/AM43XX build fixes
Date: Mon, 13 Jan 2014 19:13:20 +0200 [thread overview]
Message-ID: <52D41EB0.9010603@ti.com> (raw)
In-Reply-To: <20140113162412.GF26950@saruman.home>
On 01/13/2014 06:24 PM, Felipe Balbi wrote:
> On Fri, Jan 10, 2014 at 11:57:28AM +0200, Tero Kristo wrote:
>> The move of clock code from mach-omap2 to drivers/clk/ti introduces
>> a couple of new build errors with AM43XX/DRA7XX only builds. The
>> following patches address these issues by modifying the Kconfig + Makefile
>> under mach-omap2.
>>
>> Also, it seems DRA7XX only build is not possible at the moment, added
>> patch #2 to fix this.
>
> looks like we still need some extra patches since OMAP2-only builds
> still fail :-(
>
> Also omap1_defconfig fails miserably :-(
>
> hoping this can still get fixed in time for 3.14 :-s
Yeah, should be simple enough to fix those... Will look at these tomorrow.
Just wondering, who cares about omap1 / omap2 anyway these days? :)
Basically I overlooked both with the Makefile setup I did.
-Tero
WARNING: multiple messages have this Message-ID (diff)
From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: DRA7XX/AM43XX build fixes
Date: Mon, 13 Jan 2014 19:13:20 +0200 [thread overview]
Message-ID: <52D41EB0.9010603@ti.com> (raw)
In-Reply-To: <20140113162412.GF26950@saruman.home>
On 01/13/2014 06:24 PM, Felipe Balbi wrote:
> On Fri, Jan 10, 2014 at 11:57:28AM +0200, Tero Kristo wrote:
>> The move of clock code from mach-omap2 to drivers/clk/ti introduces
>> a couple of new build errors with AM43XX/DRA7XX only builds. The
>> following patches address these issues by modifying the Kconfig + Makefile
>> under mach-omap2.
>>
>> Also, it seems DRA7XX only build is not possible at the moment, added
>> patch #2 to fix this.
>
> looks like we still need some extra patches since OMAP2-only builds
> still fail :-(
>
> Also omap1_defconfig fails miserably :-(
>
> hoping this can still get fixed in time for 3.14 :-s
Yeah, should be simple enough to fix those... Will look at these tomorrow.
Just wondering, who cares about omap1 / omap2 anyway these days? :)
Basically I overlooked both with the Makefile setup I did.
-Tero
next prev parent reply other threads:[~2014-01-13 17:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 9:57 [PATCH 0/2] ARM: DRA7XX/AM43XX build fixes Tero Kristo
2014-01-10 9:57 ` Tero Kristo
2014-01-10 9:57 ` [PATCH 1/2] ARM: DRA7XX/AM43XX: randconfig fixes Tero Kristo
2014-01-10 9:57 ` Tero Kristo
2014-01-10 16:14 ` Felipe Balbi
2014-01-10 16:14 ` Felipe Balbi
2014-01-10 9:57 ` [PATCH 2/2] ARM: DRA7XX: Add support for DRA7XX only build Tero Kristo
2014-01-10 9:57 ` Tero Kristo
2014-01-10 16:15 ` Felipe Balbi
2014-01-10 16:15 ` Felipe Balbi
2014-01-10 16:32 ` Tero Kristo
2014-01-10 16:32 ` Tero Kristo
2014-01-13 16:24 ` [PATCH 0/2] ARM: DRA7XX/AM43XX build fixes Felipe Balbi
2014-01-13 16:24 ` Felipe Balbi
2014-01-13 17:13 ` Tero Kristo [this message]
2014-01-13 17:13 ` Tero Kristo
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=52D41EB0.9010603@ti.com \
--to=t-kristo@ti.com \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=tony@atomide.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.