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:	Mon, 15 Jun 2015 21:39:39 +0800
From:	kbuild test robot <fengguang.wu@...el.com>
To:	Gwendal Grignou <gwendal@...omium.org>
Cc:	kbuild-all@...org, Lee Jones <lee.jones@...aro.org>,
	Dmitry Torokhov <dtor@...omium.org>,
	Javier Martinez Canillas <javier.martinez@...labora.co.uk>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	linux-kernel@...r.kernel.org
Subject: [ljones-mfd:ib-mfd-i2c-input-chrome-4.2 8/10]
 drivers/mfd/cros_ec.c:30:25: sparse: symbol 'ec_p' was not declared. Should
 it be static?

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git ib-mfd-i2c-input-chrome-4.2
head:   ff4378f4b813d5aa26bbf814a9060638dab1fbbf
commit: 57b33ff077beebb68481a2b6b8e5fe58ca998169 [8/10] mfd: cros_ec: Support multiple EC in a system
reproduce:
  # apt-get install sparse
  git checkout 57b33ff077beebb68481a2b6b8e5fe58ca998169
  make ARCH=x86_64 allmodconfig
  make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> drivers/mfd/cros_ec.c:30:25: sparse: symbol 'ec_p' was not declared. Should it be static?
>> drivers/mfd/cros_ec.c:40:17: sparse: symbol 'ec_cell' was not declared. Should it be static?
>> drivers/mfd/cros_ec.c:46:17: sparse: symbol 'ec_pd_cell' 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