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:25:31 -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-f52.google.com ([209.85.218.52]:33768 "EHLO mail-oi0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1034145AbcJ0XZd (ORCPT ); Thu, 27 Oct 2016 19:25:33 -0400 In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Alexander Potapenko Cc: Stephen Rothwell , Andrey Ryabinin , Dmitry Vyukov , linux-next , Linux Kernel Mailing List On Thu, Oct 27, 2016 at 4:05 PM, Alexander Potapenko wrote: > > Maybe we could just reverse the MEMORY_HOTPLUG->!KASAN dependency to > make it KASAN->!MEMORY_HOTPLUG? Yes, that was my initial approach too, but then I decided that I'd rather build-test both together anyway. Since I can. So that just gets me the best of both worlds. We've had issues like this before, and "make allmodconfig" will never enable _everything_ (ie you always have to make some choices that will disable other cases, if only for reasons like SLUB-vs-SLAB etc). But in general the more coverage I get from build testing (without having to do lots and lots of builds - that's what the build farms are for after I have pushed things out), the better. Linus