[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <nycvar.YFH.7.76.1804102337070.28129@cbobk.fhfr.pm>
Date: Tue, 10 Apr 2018 23:38:01 +0200 (CEST)
From: Jiri Kosina <jikos@...nel.org>
To: Josh Poimboeuf <jpoimboe@...hat.com>
cc: Joe Lawrence <joe.lawrence@...hat.com>,
live-patching@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-kernel@...r.kernel.org, Petr Mladek <pmladek@...e.com>,
Miroslav Benes <mbenes@...e.cz>,
Libor Pecháček <lpechacek@...e.com>,
Nicolai Stange <nstange@...e.de>,
Artem Savkov <asavkov@...hat.com>
Subject: Re: [PATCH v2] selftests/livepatch: introduce tests
On Tue, 10 Apr 2018, Josh Poimboeuf wrote:
> I think CONFIG_LOCKDEP is always a good idea.
FWIW CONFIG_LOCKDEP mostly enables the infrastructure, but
CONFIG_PROVE_LOCKING is what turns most of the cleverness on.
--
Jiri Kosina
SUSE Labs
Powered by blists - more mailing lists