lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 14 Apr 2015 19:52:53 +0800
From:	kbuild test robot <fengguang.wu@...el.com>
To:	Erez Shitrit <erezsh@...lanox.com>
Cc:	kbuild-all@...org, Roland Dreier <roland@...nel.org>,
	Sean Hefty <sean.hefty@...el.com>,
	Hal Rosenstock <hal.rosenstock@...il.com>,
	Doug Ledford <dledford@...hat.com>, linux-rdma@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: [amirv:for-upstream 52/62]
 drivers/infiniband/ulp/ipoib/ipoib_multicast.c:735:5: sparse: symbol
 'handle_neigh_state_change' was not declared. Should it be static?

tree:   git://flatbed.openfabrics.org/~amirv/linux.git for-upstream
head:   66a75344a2e5a8e8483cfd6ab1db1c0fbcb56fda
commit: cbaa5ae8702fea9670d77daf95f35b4d38822ad0 [52/62] IB/ipoib: Add cleanup to sendonly multicast objects [ib-next:ipoib-s1]
reproduce:
  # apt-get install sparse
  git checkout cbaa5ae8702fea9670d77daf95f35b4d38822ad0
  make ARCH=x86_64 allmodconfig
  make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> drivers/infiniband/ulp/ipoib/ipoib_multicast.c:735:5: sparse: symbol 'handle_neigh_state_change' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild                 Intel Corporation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ