From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Aguirre Rodriguez, Sergio Alberto" <saaguirre@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Nayak, Rajendra" <rnayak@ti.com>
Subject: Re: [PATCH][PM] ARM: OMAP34xx: Fix compilation warning
Date: Tue, 18 Aug 2009 11:13:43 +0200 [thread overview]
Message-ID: <87vdkljxh4.fsf@deeprootsystems.com> (raw)
In-Reply-To: <A24693684029E5489D1D202277BE89444A81FBB9@dlee02.ent.ti.com> (Aguirre Rodriguez's message of "Mon\, 17 Aug 2009 09\:46\:17 -0500")
"Aguirre Rodriguez, Sergio Alberto" <saaguirre@ti.com> writes:
> From: Sergio Aguirre <saaguirre@ti.com>
>
> This fixes the following compilation warnings:
>
> In file included from arch/arm/mach-omap2/resource34xx.c:26:
> arch/arm/mach-omap2/resource34xx.h:32: warning: function declaration isn't a prototype
> arch/arm/mach-omap2/resource34xx.h:33: warning: function declaration isn't a prototype
>
> Signed-off-by: Sergio Aguirre <saaguirre@ti.com>
Thanks, will pull into PM branch and fold into original patch which
introduced these functions.
Kevin
> ---
> arch/arm/mach-omap2/resource34xx.h | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/resource34xx.h b/arch/arm/mach-omap2/resource34xx.h
> index 5b5618a..3c70eef 100644
> --- a/arch/arm/mach-omap2/resource34xx.h
> +++ b/arch/arm/mach-omap2/resource34xx.h
> @@ -29,8 +29,8 @@
> #include <mach/omap34xx.h>
>
> extern int sr_voltagescale_vcbypass(u32 t_opp, u32 c_opp, u8 t_vsel, u8 c_vsel);
> -extern void lock_scratchpad_sem();
> -extern void unlock_scratchpad_sem();
> +extern void lock_scratchpad_sem(void);
> +extern void unlock_scratchpad_sem(void);
>
> /*
> * mpu_latency/core_latency are used to control the cpuidle C state.
> --
> 1.6.3.2
prev parent reply other threads:[~2009-08-18 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 14:46 [PATCH][PM] ARM: OMAP34xx: Fix compilation warning Aguirre Rodriguez, Sergio Alberto
2009-08-18 9:13 ` 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=87vdkljxh4.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.com \
--cc=saaguirre@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.