linux-kernel - [vfio:next 19/21] drivers/vfio/virqfd.c:19:1: sparse: symbol 'virqfd_lock' was not declared. Should it be static?

Open Source and information security mailing list archives

Message-ID: <201503170713.8J9Z1hon%fengguang.wu@intel.com>
Date:	Tue, 17 Mar 2015 07:43:20 +0800
From:	kbuild test robot <fengguang.wu@...el.com>
To:	Antonios Motakis <a.motakis@...tualopensystems.com>
Cc:	kbuild-all@...org, Alex Williamson <alex.williamson@...hat.com>,
	Baptiste Reynal <b.reynal@...tualopensystems.com>,
	kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [vfio:next 19/21] drivers/vfio/virqfd.c:19:1: sparse: symbol
 'virqfd_lock' was not declared. Should it be static?

tree:   git://github.com/awilliam/linux-vfio.git next
head:   2f51bf4be99386f49841b6365a85a5cabc148565
commit: 42ac9bd18d4fc28c36c7927847f0f6e90ecd7710 [19/21] vfio: initialize the virqfd workqueue in VFIO generic code
reproduce:
  # apt-get install sparse
  git checkout 42ac9bd18d4fc28c36c7927847f0f6e90ecd7710
  make ARCH=x86_64 allmodconfig
  make C=1 CF=-D__CHECK_ENDIAN__

sparse warnings: (new ones prefixed by >>)

>> drivers/vfio/virqfd.c:19:1: sparse: symbol 'virqfd_lock' 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/

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