From: Andrew Morton <akpm@linux-foundation.org>
To: kbuild test robot <lkp@intel.com>
Cc: Yury Norov <ynorov@caviumnetworks.com>,
kbuild-all@01.org, Noam Camus <noamca@mellanox.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Matthew Wilcox <mawilcox@microsoft.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] lib: add test for bitmap_parselist()
Date: Wed, 9 Aug 2017 13:33:09 -0700 [thread overview]
Message-ID: <20170809133309.746aafee5e22c9345debd671@linux-foundation.org> (raw)
In-Reply-To: <201708091143.QqTgSaxI%fengguang.wu@intel.com>
On Wed, 9 Aug 2017 11:28:56 +0800 kbuild test robot <lkp@intel.com> wrote:
> [auto build test WARNING on linus/master]
> [also build test WARNING on v4.13-rc4 next-20170808]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url: https://github.com/0day-ci/linux/commits/Yury-Norov/lib-make-bitmap_parselist-thread-safe-and-much-faster/20170809-105307
> config: i386-randconfig-x000-201732 (attached as .config)
> compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All warnings (new ones prefixed by >>):
>
> >> lib/test_bitmap.c:180:17: warning: large integer implicitly truncated to unsigned type [-Woverflow]
> 0xfffffffe, 0x3333333311111111, 0xffffffff77777777};
> ^~~~~~~~~~~~~~~~~~
I assume that a simple convertion to unsigned long long will fix that,
but I'll await Yuri's input (and testing).
btw, exp[] and exp2[] could be __initconst?
next prev parent reply other threads:[~2017-08-09 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 22:54 [PATCH 1/2] lib: make bitmap_parselist thread-safe and much faster Yury Norov
2017-08-07 22:54 ` [PATCH 2/2] lib: add test for bitmap_parselist() Yury Norov
2017-08-09 3:28 ` kbuild test robot
2017-08-09 20:33 ` Andrew Morton [this message]
2017-08-09 22:52 ` Yury Norov
2017-08-10 7:30 ` Rasmus Villemoes
2017-08-10 10:37 ` Yury Norov
2017-08-09 4:11 ` kbuild test robot
2017-08-09 20:28 ` Andrew Morton
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=20170809133309.746aafee5e22c9345debd671@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=lkp@intel.com \
--cc=mawilcox@microsoft.com \
--cc=mchehab@kernel.org \
--cc=noamca@mellanox.com \
--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
all inboxes | Powered by JetHome®