All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: kbuild test robot <lkp@intel.com>
Cc: Florian Westphal <fw@strlen.de>,
	kbuild-all@01.org, netdev@vger.kernel.org, tgraf@suug.ch
Subject: Re: [PATCH net] rhashtable: avoid large lock-array allocations
Date: Fri, 12 Aug 2016 04:31:39 +0200	[thread overview]
Message-ID: <20160812023139.GC5332@breakpoint.cc> (raw)
In-Reply-To: <201608121030.6oKJyu5a%fengguang.wu@intel.com>

kbuild test robot <lkp@intel.com> wrote:
> Hi Florian,
> 
> [auto build test WARNING on net/master]
> 
> url:    https://github.com/0day-ci/linux/commits/Florian-Westphal/rhashtable-avoid-large-lock-array-allocations/20160812-101458
> config: x86_64-randconfig-x015-201632 (attached as .config)
> compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
> reproduce:
>         # save the attached .config to linux build tree
>         make ARCH=x86_64 
> 
> All warnings (new ones prefixed by >>):
> 
>    In file included from lib/rhashtable.c:18:0:
>    lib/rhashtable.c: In function 'rhashtable_init':
> >> lib/rhashtable.c:34:30: warning: division by zero [-Wdiv-by-zero]
>               2 * L1_CACHE_BYTES / sizeof(spinlock_t), 1)

I will send a v2 tomorrow, perhaps its better to just go for
32UL instead of this construct after all.

  reply	other threads:[~2016-08-12  2:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-12  2:13 [PATCH net] rhashtable: avoid large lock-array allocations Florian Westphal
2016-08-12  2:27 ` kbuild test robot
2016-08-12  2:31   ` Florian Westphal [this message]
2016-08-15  4:13 ` David Miller

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=20160812023139.GC5332@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=kbuild-all@01.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=tgraf@suug.ch \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.