Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1510770

Re: linux-next: build warning in Linus' tree

Show all headers | View raw

On Thu, Oct 27, 2016 at 4:05 PM, Alexander Potapenko <glider@google.com> 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

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

linux-next: build warning in Linus' tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-10-28 00:30 +0200
  Re: linux-next: build warning in Linus' tree Linus Torvalds <torvalds@linux-foundation.org> - 2016-10-28 00:50 +0200
    Re: linux-next: build warning in Linus' tree Linus Torvalds <torvalds@linux-foundation.org> - 2016-10-28 01:10 +0200
      Re: linux-next: build warning in Linus' tree Alexander Potapenko <glider@google.com> - 2016-10-28 01:10 +0200
        Re: linux-next: build warning in Linus' tree Linus Torvalds <torvalds@linux-foundation.org> - 2016-10-28 01:30 +0200
      Re: linux-next: build warning in Linus' tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-10-28 01:50 +0200
      Re: linux-next: build warning in Linus' tree Geert Uytterhoeven <geert@linux-m68k.org> - 2016-10-29 23:30 +0200

csiph-web