[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a4896565-9586-981b-06ea-03b0b7c41476@kernel.org>
Date: Wed, 10 Apr 2019 18:25:32 -0400
From: Sinan Kaya <Okaya@...nel.org>
To: Kees Cook <keescook@...omium.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Johannes Weiner <hannes@...xchg.org>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
Nicholas Piggin <npiggin@...il.com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Vasily Gorbik <gor@...ux.ibm.com>,
Adrian Reber <adrian@...as.de>,
Richard Guy Briggs <rgb@...hat.com>
Subject: Re: [PATCH v1] init: Do not select DEBUG_KERNEL by default
On 4/10/2019 6:21 PM, Kees Cook wrote:
>> I can go after individual enables if you agree assuming Mathieu will
>> go after the changes in the other email. Let me know otherwise.
> How about you split it, but make DEBUG_KERNEL be "default EXPERT" that
> way enabling EXPERT will enable DEBUG_KERNEL still in the default
> case?
Sorry, can you explain what you mean by split?
Do you mean move the things I need out of EXPERT? or something else?
Powered by blists - more mailing lists