From: Ben Hutchings <ben@decadent.org.uk>
To: Sasha Levin <Alexander.Levin@microsoft.com>
Cc: linux-kernel@vger.kernel.org, Bastian Blank <waldi@debian.org>
Subject: [PATCH 1/2] liblockdep: Stub NMI watchdog reset
Date: Wed, 29 Aug 2018 00:57:38 +0100 [thread overview]
Message-ID: <20180828235738.GI18030@decadent.org.uk> (raw)
In-Reply-To: <20180828235656.GH18030@decadent.org.uk>
From: Bastian Blank <waldi@debian.org>
lockdep.c now includes <linux/nmi.h> and requires touch_nmi_watchdog(),
so provide those for liblockdep.
Fixes: 88f1c87de11a ("locking/lockdep: Avoid triggering hardlockup from ...")
[bwh: Write a longer description]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
---
tools/include/linux/nmi.h | 12 ++++++++++++
1 file changed, 12 insertions(+)
create mode 100644 tools/include/linux/nmi.h
diff --git a/tools/include/linux/nmi.h b/tools/include/linux/nmi.h
new file mode 100644
index 000000000000..81ffb39343cc
--- /dev/null
+++ b/tools/include/linux/nmi.h
@@ -0,0 +1,12 @@
+/* SPDX-License-Identifier: GPL-2.0 */
+/*
+ * linux/include/linux/nmi.h
+ */
+#ifndef LINUX_NMI_H
+#define LINUX_NMI_H
+
+static inline void touch_nmi_watchdog(void)
+{
+}
+
+#endif
next prev parent reply other threads:[~2018-08-28 23:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 23:56 [PATCH 0/2] Build fixes for liblockdep Ben Hutchings
2018-08-28 23:57 ` Ben Hutchings [this message]
2018-08-28 23:57 ` [PATCH 2/2] liblockdep: Stub task_struct::state Ben Hutchings
2018-08-28 23:59 ` [PATCH 0/2] Build fixes for liblockdep Ben Hutchings
2018-08-29 0:19 ` Sasha Levin
-- strict thread matches above, loose matches on Subject: below --
2018-08-28 23:36 Ben Hutchings
2018-08-28 23:37 ` [PATCH 1/2] liblockdep: Stub NMI watchdog reset Ben Hutchings
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=20180828235738.GI18030@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=Alexander.Levin@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=waldi@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.