[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <201501161021.CZOoWii2%fengguang.wu@intel.com>
Date: Fri, 16 Jan 2015 10:27:32 +0800
From: kbuild test robot <fengguang.wu@...el.com>
To: Michael Halcrow <mhalcrow@...gle.com>
Cc: kbuild-all@...org, Theodore Ts'o <tytso@....edu>,
Uday Savagaonkar <savagaon@...gle.com>,
Ildar Muslukhov <ildarm@...gle.com>,
Andreas Dilger <adilger.kernel@...ger.ca>,
linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [ext4:crypto 15/21] fs/ext4/crypto_fname.c:322:5: sparse: symbol
'ext4_fname_decrypt' was not declared. Should it be static?
tree: git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git crypto
head: e32261a72a3c0c6c59d761820d8ca8b7c90008af
commit: 6b8813e5baf3aa99baec11610cc29bc4ed20e671 [15/21] ext4 crypto: filename encryption facilities
reproduce:
# apt-get install sparse
git checkout 6b8813e5baf3aa99baec11610cc29bc4ed20e671
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> fs/ext4/crypto_fname.c:322:5: sparse: symbol 'ext4_fname_decrypt' was not declared. Should it be static?
>> fs/ext4/crypto_fname.c:380:5: sparse: symbol 'ext4_fname_encode_digest' was not declared. Should it be static?
>> fs/ext4/crypto_fname.c:479:6: sparse: symbol 'ext4_free_fname_crypto_ctx' was not declared. Should it be static?
>> fs/ext4/crypto_fname.c:532:30: sparse: symbol 'ext4_alloc_fname_crypto_ctx' 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