xfs
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

[xfs:for-next 68/70] fs/xfs/xfs_ialloc_btree.c:186:1: sparse: symbol 'xf

from [kbuild test robot] [Permanent Link][Original]
To: Dave Chinner <dchinner@xxxxxxxxxx>
Subject: [xfs:for-next 68/70] fs/xfs/xfs_ialloc_btree.c:186:1: sparse: symbol 'xfs_inobt_verify' was not declared. Should it be static?
From: kbuild test robot <fengguang.wu@xxxxxxxxx>
Date: Fri, 16 Nov 2012 14:42:42 +0800
Cc: xfs@xxxxxxxxxxx, Ben Myers <bpm@xxxxxxx>
User-agent: Heirloom mailx 12.5 6/20/10 
tree:   git://oss.sgi.com/xfs/xfs for-next
head:   1813dd64057490e7a0678a885c4fe6d02f78bdc1
commit: 612cfbfe174a89d565363fff7f3961a2dda5fb71 [68/70] xfs: add pre-write 
metadata buffer verifier callbacks


sparse warnings:

+ fs/xfs/xfs_ialloc_btree.c:186:1: sparse: symbol 'xfs_inobt_verify' was not 
declared. Should it be static?
fs/xfs/xfs_ialloc_btree.c:227:1: sparse: symbol 'xfs_inobt_read_verify' was not 
declared. Should it be static?

Please consider folding the attached diff :-)

---
0-DAY kernel build testing backend         Open Source Technology Center
Fengguang Wu, Yuanhan Liu                              Intel Corporation

Attachment: make-it-static-612cfbf.diff
Description: Text Data

[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [PATCH] xfs_quota: correctly initialise the default path, Dave Chinner
Next by Date:  [PATCH 00/15] xfs: shrinking support, Jeff Liu
Previous by Thread:  [XFS updates] XFS development tree branch, for-next, updated. v3.7-rc1-70-g1813dd6, xfs
Next by Thread:  Re: [xfs:for-next 68/70] fs/xfs/xfs_ialloc_btree.c:186:1: sparse: symbol 'xfs_inobt_verify' was not declared. Should it be static?, Dave Chinner
Indexes:  [Date] [Thread] [Top] [All Lists]