From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH/RFT 0/2] fixes for broken PM init with multi-OMAP
Date: Wed, 10 Mar 2010 08:22:32 -0800 [thread overview]
Message-ID: <87d3zci1tj.fsf@deeprootsystems.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02C46F0F96@dbde02.ent.ti.com> (Santosh Shilimkar's message of "Wed\, 10 Mar 2010 12\:15\:27 +0530")
"Shilimkar, Santosh" <santosh.shilimkar@ti.com> writes:
> Thanks Kevin,
>> -----Original Message-----
>> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Kevin
>> Hilman
>> Sent: Tuesday, March 09, 2010 10:34 PM
>> To: linux-omap@vger.kernel.org
>> Subject: [PATCH/RFT 0/2] fixes for broken PM init with multi-OMAP
>>
>> multi-OMAP builds are broken in various ways due to conditional code.
>> Here is a small series of fixes.
>>
>> Build tested: omap3_defconfig, omap_4430sdp_defconfig
>> Boot tested: omap3_defconfig on OMAP3EVM
>>
> Applied this series on l-o master (dc73899a58be5e834b8df3a9049cdb1115acf175)
> OMAP3430 SDP boots normal.
>
>> Needs boot testing on OMAP4.
>>
> OMAP4 also boots with omap3_defconfig after unchecking the reset
> unused clock check. This is known and will be fixed soon.
>
Santosh,
Thanks for testing.
Will respin removing the second FIXME you mentioned in PATCH 2.
Kevin
prev parent reply other threads:[~2010-03-10 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 17:03 [PATCH/RFT 0/2] fixes for broken PM init with multi-OMAP Kevin Hilman
2010-03-09 17:04 ` [PATCH/RFT 1/2] OMAP2: cpu_is_omap2*: optimize out unused code Kevin Hilman
2010-03-09 17:04 ` [PATCH/RFT 2/2] OMAP4: fix temporary hacks that break multi-omap PM Kevin Hilman
2010-03-10 6:48 ` Shilimkar, Santosh
2010-03-10 6:45 ` [PATCH/RFT 0/2] fixes for broken PM init with multi-OMAP Shilimkar, Santosh
2010-03-10 16:22 ` Kevin Hilman [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=87d3zci1tj.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.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.