[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7cd8fa2d-301a-5c96-ce3d-3dc373a5d8f5@linux.intel.com>
Date: Sun, 7 Apr 2019 21:02:38 +0800
From: "Li, Aubrey" <aubrey.li@...ux.intel.com>
To: Alexey Dobriyan <adobriyan@...il.com>,
Thomas Gleixner <tglx@...utronix.de>
Cc: 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 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.
Thanks,
-Aubrey
Powered by blists - more mailing lists