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 16:01:22 -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-f48.google.com ([209.85.218.48]:34223 "EHLO mail-oi0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1034178AbcJ0XBX (ORCPT ); Thu, 27 Oct 2016 19:01:23 -0400 In-Reply-To: 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:48 PM, Linus Torvalds wrote: > > I wonder if we should make KASAN depend on !COMPILE_TEST, because it > does seem to disable a lot of build-time testing. Actually, we should probably just make the MEMORY_HOTPLUG dependency be depends on COMPILE_TEST || !KASAN since the memory-hotplug code should still *build* with KASAN, it just doesn't work. That's exactly what the COMPILE_TEST config option is there for - to get build coverage even for things that aren't necessarily sane to run. I'll do that, to get my build coverage up. I really expected my allmodconfig builds to verify that I had removed the per-zone waitqueue code completely, and I'm happy that the breakage was apparently limited to that unused variable.. In the meantime, thanks for noticing and letting me know. Linus