On Mon, Nov 5, 2012 at 5:54 PM, Kees Cook <keesc...@chromium.org> wrote: > On Mon, Nov 5, 2012 at 5:22 PM, David Rientjes <rient...@google.com> wrote: >> On Mon, 5 Nov 2012, Kees Cook wrote: >> >>> diff --git a/mm/Kconfig b/mm/Kconfig >>> index a3f8ddd..679945e 100644 >>> --- a/mm/Kconfig >>> +++ b/mm/Kconfig >>> @@ -1,6 +1,5 @@ >>> config SELECT_MEMORY_MODEL >>> def_bool y >>> - depends on EXPERIMENTAL || ARCH_SELECT_MEMORY_MODEL >>> >>> choice >>> prompt "Memory model" >> >> I thought you agreed to only drop EXPERIMENTAL here in >> http://marc.info/?l=linux-kernel&m=135103415901094 and leave >> ARCH_SELECT_MEMORY_MODEL, which you've orphaned with the above, for phase >> two of your effort? > > Ah! Yes, thanks. I'll restore that.
Wait, no. This is an "OR". ARCH_SELECT_MEMORY_MODEL has no affect on SELECT_MEMORY_MODEL if EXPERIMENTAL is always considered on. My proposal was to deal with ARCH_SELECT_MEMORY_MODEL separately. Did I misunderstand something? -Kees -- Kees Cook Chrome OS Security -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/