From: jikos at kernel.org (Jiri Kosina)
Subject: [PATCH v2] selftests/livepatch: introduce tests
Date: Tue, 10 Apr 2018 23:38:01 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.1804102337070.28129@cbobk.fhfr.pm> (raw)
In-Reply-To: <20180410213354.ma5wfe3jc23pzmw4@treble>
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: jikos@kernel.org (Jiri Kosina)
Subject: [PATCH v2] selftests/livepatch: introduce tests
Date: Tue, 10 Apr 2018 23:38:01 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.1804102337070.28129@cbobk.fhfr.pm> (raw)
Message-ID: <20180410213801.DFTD_nbURxQw1ObtFE3oyReUd8xN8fCq9h9os9SRGho@z> (raw)
In-Reply-To: <20180410213354.ma5wfe3jc23pzmw4@treble>
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-04-10 21:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 15:15 [PATCH v2] Add livepatch kselftests joe.lawrence
2018-04-10 15:15 ` Joe Lawrence
2018-04-10 15:15 ` [PATCH v2] selftests/livepatch: introduce tests joe.lawrence
2018-04-10 15:15 ` Joe Lawrence
2018-04-10 20:00 ` jpoimboe
2018-04-10 20:00 ` Josh Poimboeuf
2018-04-10 20:50 ` joe.lawrence
2018-04-10 20:50 ` Joe Lawrence
2018-04-10 21:33 ` jpoimboe
2018-04-10 21:33 ` Josh Poimboeuf
2018-04-10 21:38 ` jikos [this message]
2018-04-10 21:38 ` Jiri Kosina
[not found] ` <201804111155.d856J7oR%fengguang.wu@intel.com>
2018-04-11 13:59 ` joe.lawrence
2018-04-11 13:59 ` Joe Lawrence
2018-04-13 15:49 ` [kbuild-all] " philip.li
2018-04-13 15:49 ` Philip Li
2018-04-13 20:55 ` joe.lawrence
2018-04-13 20:55 ` Joe Lawrence
2018-04-17 2:32 ` xiaolong.ye
2018-04-17 2:32 ` Ye Xiaolong
2018-04-10 20:04 ` [PATCH v2] Add livepatch kselftests jpoimboe
2018-04-10 20:04 ` Josh Poimboeuf
2018-04-12 13:28 ` mbenes
2018-04-12 13:28 ` Miroslav Benes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.YFH.7.76.1804102337070.28129@cbobk.fhfr.pm \
--to=linux-kselftest@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).