From: Kevin Hilman <khilman@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: Tony <tony@atomide.com>, l-o <linux-omap@vger.kernel.org>,
l-a <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] OMAP3+: sr_device: include pm header
Date: Wed, 05 Jan 2011 16:28:01 -0800 [thread overview]
Message-ID: <87y66yub8u.fsf@ti.com> (raw)
In-Reply-To: <1294083341-32147-1-git-send-email-nm@ti.com> (Nishanth Menon's message of "Mon, 3 Jan 2011 13:35:41 -0600")
Nishanth Menon <nm@ti.com> writes:
> omap_enable_smartreflex_on_init is meant to be used by boards
> which would like to have SR enabled by default on the platform, while
> omap_devinit_smartreflex is used by pm code, the protos are defined
> in pm.h. This header should be included to ensure that sr_device
> function definitions match the prototypes.
>
> including pm.h fixes the sparse warnings (with CONFIG_OMAP_SMARTREFLEX=y):
> arch/arm/mach-omap2/sr_device.c:138:13: warning: symbol 'omap_enable_smartreflex_on_init' was not declared. Should it be static?
> arch/arm/mach-omap2/sr_device.c:143:12: warning: symbol 'omap_devinit_smartreflex' was not declared. Should it be static?
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
Thanks, will queue as a fix for 2.6.38-rc cycle.
Kevin
> Based on:
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git
> branch: omap-for-linus
>
> arch/arm/mach-omap2/sr_device.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/sr_device.c b/arch/arm/mach-omap2/sr_device.c
> index 786d685..b1e0af1 100644
> --- a/arch/arm/mach-omap2/sr_device.c
> +++ b/arch/arm/mach-omap2/sr_device.c
> @@ -27,6 +27,7 @@
> #include <plat/voltage.h>
>
> #include "control.h"
> +#include "pm.h"
>
> static bool sr_enable_on_init;
prev parent reply other threads:[~2011-01-06 0:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 19:35 [PATCH] OMAP3+: sr_device: include pm header Nishanth Menon
2011-01-06 0:28 ` 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=87y66yub8u.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox