[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120814200110.GE5277@herton-Z68MA-D2H-B3>
Date: Tue, 14 Aug 2012 17:01:11 -0300
From: Herton Ronaldo Krzesinski <herton.krzesinski@...onical.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
alan@...rguk.ukuu.org.uk, Colin Cross <ccross@...roid.com>,
Barry Song <bs14@....com>,
Catalin Marinas <catalin.marinas@....com>,
Ido Yariv <ido@...ery.com>, Daniel Drake <dsd@...top.org>,
Will Deacon <will.deacon@....com>,
Russell King <rmk+kernel@....linux.org.uk>
Subject: Re: [ 07/44] ARM: 7477/1: vfp: Always save VFP state in
vfp_pm_suspend on UP
On Mon, Aug 13, 2012 at 03:02:14PM -0700, Greg Kroah-Hartman wrote:
> From: Greg KH <gregkh@...uxfoundation.org>
>
[...]
> --- a/arch/arm/vfp/vfpmodule.c
> +++ b/arch/arm/vfp/vfpmodule.c
> @@ -412,6 +412,12 @@ static int vfp_pm_suspend(void)
>
> /* disable, just in case */
> fmxr(FPEXC, fmrx(FPEXC) & ~FPEXC_EN);
> + } else if (vfp_current_hw_state[ti->cpu]) {
> +#ifndef CONFIG_SMP
> + fmxr(FPEXC, fpexc | FPEXC_EN);
> + vfp_save_state(vfp_current_hw_state[ti->cpu], fpexc);
> + fmxr(FPEXC, fpexc);
> +#endif
This fails to build on 3.0:
linux-stable/arch/arm/vfp/vfpmodule.c: In function 'vfp_pm_suspend':
linux-stable/arch/arm/vfp/vfpmodule.c:415:13: error: 'vfp_current_hw_state' undeclared (first use in this function)
linux-stable/arch/arm/vfp/vfpmodule.c:415:13: note: each undeclared identifier is reported only once for each function it appears in
make[3]: *** [arch/arm/vfp/vfpmodule.o] Error 1
In 3.0, vfp_current_hw_state was still named last_VFP_context, so I
think just renaming should be enough to fix this.
> }
>
> /* clear any information we had about last context state */
>
--
[]'s
Herton
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists