From: Nicholas Piggin <npiggin@gmail.com>
To: Don Zickus <dzickus@redhat.com>
Cc: Nicholas Piggin <npiggin@gmail.com>, linux-kernel@vger.kernel.org
Subject: [PATCH 1/5] watchdog: remove unused declaration
Date: Mon, 22 May 2017 23:03:59 +1000 [thread overview]
Message-ID: <20170522130403.18551-2-npiggin@gmail.com> (raw)
In-Reply-To: <20170522130403.18551-1-npiggin@gmail.com>
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
---
include/linux/nmi.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/include/linux/nmi.h b/include/linux/nmi.h
index aa3cd0878270..5e2e57536d98 100644
--- a/include/linux/nmi.h
+++ b/include/linux/nmi.h
@@ -12,9 +12,6 @@ extern void touch_softlockup_watchdog_sched(void);
extern void touch_softlockup_watchdog(void);
extern void touch_softlockup_watchdog_sync(void);
extern void touch_all_softlockup_watchdogs(void);
-extern int proc_dowatchdog_thresh(struct ctl_table *table, int write,
- void __user *buffer,
- size_t *lenp, loff_t *ppos);
extern unsigned int softlockup_panic;
extern unsigned int hardlockup_panic;
void lockup_detector_init(void);
--
2.11.0
next prev parent reply other threads:[~2017-05-22 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 13:03 [PATCH 0/5] Improve watchdog config for arch watchdogs Nicholas Piggin
2017-05-22 13:03 ` Nicholas Piggin [this message]
2017-05-22 13:04 ` [PATCH 2/5] watchdog: Introduce arch_touch_nmi_watchdog() Nicholas Piggin
2017-05-22 13:04 ` [PATCH 3/5] watchdog: Split up config options Nicholas Piggin
2017-05-23 14:51 ` kbuild test robot
2017-05-22 13:04 ` [PATCH 4/5] watchdog: Provide watchdog_reconfigure() for arch watchdogs Nicholas Piggin
2017-05-23 14:17 ` kbuild test robot
2017-05-22 13:04 ` [PATCH 5/5] powerpc/64s: SMP hardlockup watchdog Nicholas Piggin
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=20170522130403.18551-2-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=dzickus@redhat.com \
--cc=linux-kernel@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