From: Romit Dasgupta <romit@ti.com>
To: Eduardo Valentin <eduardo.valentin@nokia.com>
Cc: ext Kevin Hilman <khilman@deeprootsystems.com>,
"Menon, Nishanth" <nm@ti.com>,
"\"Keski-Saari Juha.1 (EXT-Teleca/Helsinki)\""
<ext-juha.1.keski-saari@nokia.com>,
"Cousson, Benoit" <b-cousson@ti.com>,
Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: [PATCHv3 1/1] OMAP3: PM: move omap opp layer from pm34xx.c
Date: Wed, 20 Jan 2010 16:43:17 +0530 [thread overview]
Message-ID: <4B56E54D.4070304@ti.com> (raw)
In-Reply-To: <1263983963-18480-1-git-send-email-eduardo.valentin@nokia.com>
> From: Eduardo Valentin <eduardo.valentin@nokia.com>
>
> OMAP OPP layer functions now have dependencies of CONFIG_CPU_FREQ only.
>
> With this patch, omap opp layer now has its compilation flags
> bound to CONFIG_CPU_FREQ. Also its code has been removed from pm34xx.c.
>
> A new file has been created to contain cpu freq code related to
> OMAP3: cpufreq34xx.c.
>
> Signed-off-by: Eduardo Valentin <eduardo.valentin@nokia.com>
> ---
> arch/arm/mach-omap2/Makefile | 5 +
NAK. Your kernel will not boot if you build it without CONFIG_CPU_FREQ.
next prev parent reply other threads:[~2010-01-20 11:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 10:39 [PATCHv3 1/1] OMAP3: PM: move omap opp layer from pm34xx.c Eduardo Valentin
2010-01-20 11:13 ` Romit Dasgupta [this message]
2010-01-20 11:51 ` Eduardo Valentin
2010-01-20 11:52 ` Romit Dasgupta
2010-01-20 11:14 ` Romit Dasgupta
2010-01-20 11:54 ` Eduardo Valentin
2010-01-20 12:00 ` Romit Dasgupta
2010-01-20 12:40 ` Eduardo Valentin
2010-01-20 12:44 ` Romit Dasgupta
2010-01-20 12:49 ` Eduardo Valentin
2010-01-20 12:54 ` Romit Dasgupta
2010-01-20 14:20 ` Eduardo Valentin
2010-01-21 7:16 ` Romit Dasgupta
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=4B56E54D.4070304@ti.com \
--to=romit@ti.com \
--cc=b-cousson@ti.com \
--cc=eduardo.valentin@nokia.com \
--cc=ext-juha.1.keski-saari@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--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.