Though I don't mind seeing parts of the internals of lustre passing by on the mailing list, I am wondering is this the right list for them? On Mon, Dec 8, 2014 at 11:52 AM, Fred Chou <fred.chou.nd(a)gmail.com&gt; wrote: > From: Fred Chou <fred.chou.nd(a)gmail.com&gt; > > Fixed the below warning in sparse: > > drivers/staging/lustre/lustre/ptlrpc/lproc_ptlrpc.c:184:6: > warning: symbol 'ptlrpc_lprocfs_register' was not declared. > Should it be static? > > Signed-off-by: Fred Chou <fred.chou.nd(a)gmail.com&gt; > --- > drivers/staging/lustre/lustre/ptlrpc/lproc_ptlrpc.c | 7 ++++--- > 1 file changed, 4 insertions(+), 3 deletions(-) > > diff --git a/drivers/staging/lustre/lustre/ptlrpc/lproc_ptlrpc.c >b/drivers/staging/lustre/lustre/ptlrpc/lproc_ptlrpc.c > index 4011e00..4c0d48e 100644 > --- a/drivers/staging/lustre/lustre/ptlrpc/lproc_ptlrpc.c > +++ b/drivers/staging/lustre/lustre/ptlrpc/lproc_ptlrpc.c > @@ -181,9 +181,10 @@ const char *ll_eopcode2str(__u32 opcode) > return ll_eopcode_table[opcode].opname; > } > #if defined (CONFIG_PROC_FS) > -void ptlrpc_lprocfs_register(struct proc_dir_entry *root, char *dir, > - char *name, struct proc_dir_entry >**procroot_ret, > - struct lprocfs_stats **stats_ret) > +static void ptlrpc_lprocfs_register(struct proc_dir_entry *root, char >*dir, > + char *name, > + struct proc_dir_entry >**procroot_ret, > + struct lprocfs_stats **stats_ret) > { > struct proc_dir_entry *svc_procroot; > struct lprocfs_stats *svc_stats; > -- > 1.9.1 > > _______________________________________________ > HPDD-discuss mailing list > HPDD-discuss(a)lists.01.org > https://lists.01.org/mailman/listinfo/hpdd-discuss _______________________________________________ HPDD-discuss mailing list HPDD-discuss(a)lists.01.org https://lists.01.org/mailman/listinfo/hpdd-discuss