[Skiboot] [PATCH 17/25] sparse: epow_status can be static

[Vasant Hegde]

On 02/24/2015 04:44 PM, Cédric Le Goater wrote:
> Signed-off-by: Cédric Le Goater <clg at fr.ibm.com>


Acked-by: Vasant Hegde <hegdevasant at linux.vnet.ibm.com>

-Vasant


> ---
>  hw/fsp/fsp-epow.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/hw/fsp/fsp-epow.c b/hw/fsp/fsp-epow.c
> index dba05cbcce7d..ed91c15a726c 100644
> --- a/hw/fsp/fsp-epow.c
> +++ b/hw/fsp/fsp-epow.c
> @@ -41,7 +41,7 @@
>   * more of power subsystem specific EPOW events like OPAL_SYSPOWER_UPS,
>   * OPAL_SYSPOWER_CHNG, OPAL_SYSPOWER_FAIL or OPAL_SYSPOWER_INCL.
>   */
> -int16_t epow_status[OPAL_SYSEPOW_MAX];
> +static int16_t epow_status[OPAL_SYSEPOW_MAX];
>  
>  /* EPOW lock */
>  static struct lock epow_lock = LOCK_UNLOCKED;
>