From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755008AbcJ2V3f (ORCPT ); Sat, 29 Oct 2016 17:29:35 -0400 Received: from mail-it0-f47.google.com ([209.85.214.47]:37452 "EHLO mail-it0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751547AbcJ2V3d (ORCPT ); Sat, 29 Oct 2016 17:29:33 -0400 MIME-Version: 1.0 In-Reply-To: References: <20161028092920.4d84f8f1@canb.auug.org.au> From: Geert Uytterhoeven Date: Sat, 29 Oct 2016 23:29:32 +0200 X-Google-Sender-Auth: BHgb3EGqqauzKsNM00lzQtQLdMo Message-ID: Subject: Re: linux-next: build warning in Linus' tree To: Linus Torvalds Cc: Stephen Rothwell , Andrey Ryabinin , Alexander Potapenko , Dmitry Vyukov , linux-next , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Linus, On Fri, Oct 28, 2016 at 1:01 AM, Linus Torvalds wrote: > 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. In what way does it not work? Does it crash? People do run COMPILE_TEST=y/allmodconfig kernels. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds