* [nfs:linux-next 50/51] fs/nfs/flexfilelayout/flexfilelayout.c:187:1: sparse: symbol 'ff_layout_remove_mirror' was not declared. Should it be static?
@ 2015-08-25 3:19 kbuild test robot
2015-08-25 3:19 ` [PATCH nfs] NFSv4.1/flexfile: ff_layout_remove_mirror can be static kbuild test robot
0 siblings, 1 reply; 2+ messages in thread
From: kbuild test robot @ 2015-08-25 3:19 UTC (permalink / raw)
To: Trond Myklebust; +Cc: kbuild-all, linux-nfs
tree: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
head: fd263b4f66bc592fe429f155d6bd20a25d3b6615
commit: 87cb6090f01142079e37dbbc8ab9db2625694ae0 [50/51] NFSv4.1/flexfile: Ensure uniqueness of mirrors across layout segments
reproduce:
# apt-get install sparse
git checkout 87cb6090f01142079e37dbbc8ab9db2625694ae0
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> fs/nfs/flexfilelayout/flexfilelayout.c:187:1: sparse: symbol 'ff_layout_remove_mirror' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-08-25 3:22 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-08-25 3:19 [nfs:linux-next 50/51] fs/nfs/flexfilelayout/flexfilelayout.c:187:1: sparse: symbol 'ff_layout_remove_mirror' was not declared. Should it be static? kbuild test robot
2015-08-25 3:19 ` [PATCH nfs] NFSv4.1/flexfile: ff_layout_remove_mirror can be static kbuild test robot
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.