From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Subject: Re: linux-next: build warning in Linus' tree Date: Thu, 27 Oct 2016 15:48:37 -0700 Message-ID: References: <20161028092920.4d84f8f1@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mail-oi0-f50.google.com ([209.85.218.50]:34650 "EHLO mail-oi0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S942804AbcJ0Wsj (ORCPT ); Thu, 27 Oct 2016 18:48:39 -0400 In-Reply-To: <20161028092920.4d84f8f1@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell , Andrey Ryabinin , Alexander Potapenko , Dmitry Vyukov Cc: linux-next , Linux Kernel Mailing List On Thu, Oct 27, 2016 at 3:29 PM, Stephen Rothwell wrote: > > Building your tree, today's linux-next build (powerpc ppc64_defconfig) > produced this warning: > > mm/memory_hotplug.c: In function 'try_offline_node': > mm/memory_hotplug.c:2120:6: warning: unused variable 'i' [-Wunused-variable] > int i; > ^ > > Introduced by commit > > 9dcb8b685fc3 ("mm: remove per-zone hashtable of bitlock waitqueues") Strange. I wonder why I didn't see that warning. Not with allmodconfig, and not with my normal build. [ Looks around ] Hmm. Apparently "allmodconfig" doesn't actually enable memory hotplug. And the reason is that allmodconfig enables KASAN, which then disables MEMORY_HOTPLUG. I wonder if we should make KASAN depend on !COMPILE_TEST, because it does seem to disable a lot of build-time testing. Oh well. I'll remove the stupid unused variable, thanks for the heads-up. Linus