netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [net-next:master 1142/1149] net/tipc/discover.c:137:6: sparse: symbol 'tipc_disc_addr_trial_msg' was not declared. Should it be static?
@ 2018-03-23 19:47 kbuild test robot
  2018-03-23 19:47 ` [RFC PATCH net-next] tipc: tipc_disc_addr_trial_msg() can be static kbuild test robot
  0 siblings, 1 reply; 4+ messages in thread
From: kbuild test robot @ 2018-03-23 19:47 UTC (permalink / raw)
  To: Jon Maloy; +Cc: kbuild-all, netdev, Ying Xue, tipc-discussion, linux-kernel

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
head:   f452518c982e57538e6d49da0a2c80eef22087ab
commit: 25b0b9c4e835ffaa65b61c3efe2e28acf84d0259 [1142/1149] tipc: handle collisions of 32-bit node address hash values
reproduce:
        # apt-get install sparse
        git checkout 25b0b9c4e835ffaa65b61c3efe2e28acf84d0259
        make ARCH=x86_64 allmodconfig
        make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> net/tipc/discover.c:137:6: sparse: symbol 'tipc_disc_addr_trial_msg' 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] 4+ messages in thread

end of thread, other threads:[~2018-03-26  1:23 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-03-23 19:47 [net-next:master 1142/1149] net/tipc/discover.c:137:6: sparse: symbol 'tipc_disc_addr_trial_msg' was not declared. Should it be static? kbuild test robot
2018-03-23 19:47 ` [RFC PATCH net-next] tipc: tipc_disc_addr_trial_msg() can be static kbuild test robot
2018-03-24 12:57   ` Jon Maloy
2018-03-26  1:23   ` David Miller

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).