[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190407154622.GA16004@avx2>
Date: Sun, 7 Apr 2019 18:46:22 +0300
From: Alexey Dobriyan <adobriyan@...il.com>
To: "Li, Aubrey" <aubrey.li@...ux.intel.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, mingo@...hat.com,
Peter Zijlstra <peterz@...radead.org>,
"H. Peter Anvin" <hpa@...or.com>, ak@...ux.intel.com,
tim.c.chen@...ux.intel.com, dave.hansen@...el.com,
arjan@...ux.intel.com, aubrey.li@...el.com,
LKML <linux-kernel@...r.kernel.org>,
Linux API <linux-api@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH v13 1/3] /proc/pid/status: Add support for architecture
specific output
On Sun, Apr 07, 2019 at 09:02:38PM +0800, Li, Aubrey wrote:
> On 2019/4/7 5:41, Alexey Dobriyan wrote:
> > On Fri, Apr 05, 2019 at 09:32:35PM +0200, Thomas Gleixner wrote:
> >>> +/* Add support for architecture specific output in /proc/pid/status */
> >>> +extern void arch_proc_pid_status(struct seq_file *m, struct task_struct *task);
> > ^^^^^^
> >
> > Unnecessary extern.
> >
> The linkage is default extern, but with this functions and variables
> can be treated the same way.
>
> Is it mandatory not to use it explicitly? ./script/checkpatch.pl did
> not report this.
"extern" is only necessary for variables. For prototypes, it is more typing
and more characters on the screen.
checkpatch.pl doesn't report it because opening floodgates is not the plan.
Yours,
Extern Police.
Powered by blists - more mailing lists