[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50A674D2.9080403@gmail.com>
Date: Fri, 16 Nov 2012 21:16:02 +0400
From: Igor Mazanov <i.mazanov@...il.com>
To: Paul Walmsley <paul@...an.com>
CC: mturquette@...com, linux-omap@...r.kernel.org, tony@...mide.com,
linux@....linux.org.uk, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Remove inline from clock framework function definitions
to build the kernel with GCC 4.7
Paul Walmsley wrote:
> + Mike
>
> On Thu, 15 Nov 2012, Igor Mazanov wrote:
>
>> Remove inline from clock framework function definitions to
>> build the kernel with GCC 4.7
>
> sparse warns about this also.
>
>> Signed-off-by: Igor Mazanov <i.mazanov@...il.com>
>
> This one is for Mike to deal with as CCF maintainer; it's out of the hands
> of the OMAP folks.
Thanks for comments, I'll bear in mind it for the future.
>
> Acked-by: Paul Walmsley <paul@...an.com>
>
>
>> ---
>> include/linux/clk-provider.h | 4 ++--
>> 1 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/include/linux/clk-provider.h b/include/linux/clk-provider.h
>> index c127315..f9f5e9e 100644
>> --- a/include/linux/clk-provider.h
>> +++ b/include/linux/clk-provider.h
>> @@ -335,8 +335,8 @@ const char *__clk_get_name(struct clk *clk);
>> struct clk_hw *__clk_get_hw(struct clk *clk);
>> u8 __clk_get_num_parents(struct clk *clk);
>> struct clk *__clk_get_parent(struct clk *clk);
>> -inline int __clk_get_enable_count(struct clk *clk);
>> -inline int __clk_get_prepare_count(struct clk *clk);
>> +int __clk_get_enable_count(struct clk *clk);
>> +int __clk_get_prepare_count(struct clk *clk);
>> unsigned long __clk_get_rate(struct clk *clk);
>> unsigned long __clk_get_flags(struct clk *clk);
>> int __clk_is_enabled(struct clk *clk);
>> --
>> 1.7.4.4
>>
>
>
> - Paul
--
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