[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20221011031104.5gvw47ocbhj52oxy@vireshk-i7>
Date: Tue, 11 Oct 2022 08:41:04 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Stephen Boyd <sboyd@...nel.org>
Cc: Michael Turquette <mturquette@...libre.com>,
Russell King <linux@...linux.org.uk>,
Shiraz Hashim <shiraz.linux.kernel@...il.com>,
Viresh Kumar <vireshk@...nel.org>, soc@...nel.org,
kernel test robot <lkp@...el.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-clk@...r.kernel.org
Subject: Re: [PATCH] clk: spear: Move prototype to accessible header
On 10-10-22, 18:01, Stephen Boyd wrote:
> __init is meaningless in header files
Technically yes.
But then I grepped include/ and it is widely used, even by core kernel
headers. Why is that ? Maybe just to keep prototype consistent ?
Also init.h says:
* If the function has a prototype somewhere, you can also add
* __init between closing brace of the prototype and semicolon:
*
* extern int initialize_foobar_device(int, int, int) __init;
Hmm, I understand that it is just saying that __init can be used after
function's name instead of just before, but isn't it also suggesting
that headers may also have it (maybe just to keep it consistent) ?
--
viresh
Powered by blists - more mailing lists