From: Kevin Hilman <khilman@deeprootsystems.com>
To: Nishanth Menon <nm@ti.com>
Cc: Manjunatha GK <manjugk@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] OMAP3: PM: Fix zoom3 defconfig build
Date: Mon, 26 Apr 2010 11:11:52 -0700 [thread overview]
Message-ID: <87bpd6ulqv.fsf@deeprootsystems.com> (raw)
In-Reply-To: <4BD5AA4F.800@ti.com> (Nishanth Menon's message of "Mon\, 26 Apr 2010 09\:59\:27 -0500")
Nishanth Menon <nm@ti.com> writes:
> Manjunatha GK had written, on 04/26/2010 08:18 AM, the following:
>> The zoom3 defconfig build is broken with opp patches.
>> This patch will fix the same. Build and boot tested on
>> omap zoom3 board.
>>
>> Build error log:
>> In file included from arch/arm/plat-omap/include/plat/omap-pm.h:21,
>> from arch/arm/mach-omap2/hsmmc.c:19:
>> arch/arm/plat-omap/include/plat/opp.h: In function 'opp_find_freq_exact':
>> arch/arm/plat-omap/include/plat/opp.h:255: error: implicit declaration of function 'ERR_PTR'
>
> I think this is a valid change, though I think commit message is not
> informative enough in this case. the problem is that opp.h defines a
> set of empty access functions for use when CPUFREQ is not defined,
> which is the case you seem to be hitting. it is not restricted to
> zoom3 defconfig.
>
> If you could rephrase the commit message accordingly, it would be helpful.
No need... I found a few other problems related to CPUfreq not being
enabled and I folded the fixes into the original commits and rebase
pm-opp.
Kevin
prev parent reply other threads:[~2010-04-26 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 13:18 [PATCH] OMAP3: PM: Fix zoom3 defconfig build Manjunatha GK
2010-04-26 14:59 ` Nishanth Menon
2010-04-26 18:11 ` 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=87bpd6ulqv.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=manjugk@ti.com \
--cc=nm@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.