[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <201508040215.7qWcXFTI%fengguang.wu@intel.com>
Date: Tue, 4 Aug 2015 02:47:48 +0800
From: kbuild test robot <fengguang.wu@...el.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: linux-kernel@...r.kernel.org
Subject: [tip:locking/core 19/20] lib/test_static_keys.c:23:19: sparse:
symbol 'old_true_key' was not declared. Should it be static?
tree: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/core
head: 412758cb26704e5087ca2976ec3b28fb2bdbfad4
commit: 2bf9e0ab08c64ac56067555911a1ae81ebff5f96 [19/20] locking/static_keys: Provide a selftest
reproduce:
# apt-get install sparse
git checkout 2bf9e0ab08c64ac56067555911a1ae81ebff5f96
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> lib/test_static_keys.c:23:19: sparse: symbol 'old_true_key' was not declared. Should it be static?
>> lib/test_static_keys.c:24:19: sparse: symbol 'old_false_key' was not declared. Should it be static?
>> lib/test_static_keys.c:27:1: sparse: symbol 'true_key' was not declared. Should it be static?
>> lib/test_static_keys.c:28:1: sparse: symbol 'false_key' was not declared. Should it be static?
>> lib/test_static_keys.c:73:5: sparse: symbol 'verify_keys' 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