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-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 15 Oct 2015 04:52:17 +0800
From:	kbuild test robot <lkp@...el.com>
To:	Matias Bjørling <m@...rling.me>
Cc:	kbuild-all@...org, hch@...radead.org, axboe@...com,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-nvme@...ts.infradead.org, keith.busch@...el.com,
	jg@...htnvm.io, Stephen.Bates@...s.com,
	Matias Bjørling <m@...rling.me>
Subject: Re: [PATCH v10 1/5] lightnvm: Support for Open-Channel SSDs

Hi Matias,

[auto build test WARNING on block/for-next -- if it's inappropriate base, please suggest rules for selecting the more suitable base]

url:    https://github.com/0day-ci/linux/commits/Matias-Bj-rling/Support-for-Open-Channel-SSDs/20151014-224617
reproduce:
        # apt-get install sparse
        make ARCH=x86_64 allmodconfig
        make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> drivers/lightnvm/core.c:37:21: sparse: symbol 'nvm_find_target_type' was not declared. Should it be static?
>> drivers/lightnvm/core.c:126:16: sparse: symbol 'nvm_find_nvm_dev' was not declared. Should it be static?
>> drivers/lightnvm/core.c:212:5: sparse: symbol 'nvm_validate_features' was not declared. Should it be static?
>> drivers/lightnvm/core.c:226:5: sparse: symbol 'nvm_validate_responsibility' was not declared. Should it be static?
>> drivers/lightnvm/core.c:234:5: sparse: symbol 'nvm_init' was not declared. Should it be static?
>> drivers/lightnvm/core.c:307:6: sparse: symbol 'nvm_exit' 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
--
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