[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <52392d47-4b69-2353-b831-6db4250bed78@au1.ibm.com>
Date: Thu, 14 Mar 2019 11:09:42 +1100
From: Andrew Donnellan <andrew.donnellan@....ibm.com>
To: Daniel Axtens <dja@...ens.net>,
"Alastair D'Silva" <alastair@....ibm.com>
Cc: Michal Hocko <mhocko@...e.com>,
Mahesh Salgaonkar <mahesh@...ux.vnet.ibm.com>,
"Alastair D'Silva" <alastair@...ilva.org>,
linux-kernel@...r.kernel.org, Nicholas Piggin <npiggin@...il.com>,
Mike Rapoport <rppt@...ux.vnet.ibm.com>,
Paul Mackerras <paulus@...ba.org>,
"Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>,
linuxppc-dev@...ts.ozlabs.org,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 1/1] arch/powerpc: Rework local_paca to avoid LTO warnings
On 14/3/19 10:54 am, Daniel Axtens wrote:
>> +static inline struct paca_struct *get_paca_no_preempt_check(void)
>> +{
>> + register struct paca_struct *paca asm("r13");
>> + return paca;
>> +}
>
> Isn't the convention to have the { on the same line as the function, or
> am I horrible mis-remembering things?
However, there is one special case, namely functions: they have the
opening brace at the beginning of the next line, thus:
int function(int x)
{
body of function
}
Heretic people all over the world have claimed that this inconsistency
is ... well ... inconsistent, but all right-thinking people know that
(a) K&R are **right** and (b) K&R are right. Besides, functions are
special anyway (you can't nest them in C).
--
Andrew Donnellan OzLabs, ADL Canberra
andrew.donnellan@....ibm.com IBM Australia Limited
Powered by blists - more mailing lists