From: kbuild test robot <fengguang.wu@intel.com>
To: Yury Norov <ynorov@caviumnetworks.com>
Cc: kbuild-all@01.org, Clement Courbet <courbet@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 12909/13131] lib/test_find_bit.c:54:2: warning: format '%ld' expects argument of type 'long int', but argument 2 has type 'cycles_t'
Date: Tue, 14 Nov 2017 00:34:13 +0800 [thread overview]
Message-ID: <201711140010.NB06960r%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2636 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: c348a99ee55feac43b5b62a5957c6d8e2b6c3abe
commit: 09588b1f1d585719b641ca55e6a3ec3db8e06a07 [12909/13131] lib: test module for find_*_bit() functions
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 09588b1f1d585719b641ca55e6a3ec3db8e06a07
# save the attached .config to linux build tree
make.cross ARCH=xtensa
All warnings (new ones prefixed by >>):
lib/test_find_bit.c: In function 'test_find_first_bit':
>> lib/test_find_bit.c:54:2: warning: format '%ld' expects argument of type 'long int', but argument 2 has type 'cycles_t' [-Wformat=]
pr_err("find_first_bit:\t\t%ld cycles,\t%ld iterations\n", cycles, cnt);
^
lib/test_find_bit.c: In function 'test_find_next_bit':
lib/test_find_bit.c:68:2: warning: format '%ld' expects argument of type 'long int', but argument 2 has type 'cycles_t' [-Wformat=]
pr_err("find_next_bit:\t\t%ld cycles,\t%ld iterations\n", cycles, cnt);
^
lib/test_find_bit.c: In function 'test_find_next_zero_bit':
lib/test_find_bit.c:82:2: warning: format '%ld' expects argument of type 'long int', but argument 2 has type 'cycles_t' [-Wformat=]
pr_err("find_next_zero_bit:\t%ld cycles,\t%ld iterations\n",
^
lib/test_find_bit.c: In function 'test_find_last_bit':
lib/test_find_bit.c:102:2: warning: format '%ld' expects argument of type 'long int', but argument 2 has type 'cycles_t' [-Wformat=]
pr_err("find_last_bit:\t\t%ld cycles,\t%ld iterations\n", cycles, cnt);
^
vim +54 lib/test_find_bit.c
38
39 /*
40 * This is Schlemiel the Painter's algorithm. It should be called after
41 * all other tests for the same bitmap because it sets all bits of bitmap to 1.
42 */
43 static int __init test_find_first_bit(void *bitmap, unsigned long len)
44 {
45 unsigned long i, cnt;
46 cycles_t cycles;
47
48 cycles = get_cycles();
49 for (cnt = i = 0; i < len; cnt++) {
50 i = find_first_bit(bitmap, len);
51 __clear_bit(i, bitmap);
52 }
53 cycles = get_cycles() - cycles;
> 54 pr_err("find_first_bit:\t\t%ld cycles,\t%ld iterations\n", cycles, cnt);
55
56 return 0;
57 }
58
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 51528 bytes --]
reply other threads:[~2017-11-13 16:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201711140010.NB06960r%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=courbet@google.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=ynorov@caviumnetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox