From: Peter Zijlstra <peterz@infradead.org>
To: Don Zickus <dzickus@redhat.com>
Cc: x86@kernel.org, Andi Kleen <andi@firstfloor.org>,
Robert Richter <robert.richter@amd.com>,
ying.huang@intel.com, LKML <linux-kernel@vger.kernel.org>,
paulmck@linux.vnet.ibm.com, avi@redhat.com, jeremy@goop.org
Subject: Re: [V7][PATCH 0/6] x86, nmi: new NMI handling routines
Date: Mon, 03 Oct 2011 17:52:38 +0200 [thread overview]
Message-ID: <1317657158.20367.30.camel@twins> (raw)
In-Reply-To: <1317409584-23662-1-git-send-email-dzickus@redhat.com>
Also fixed:
drivers/char/ipmi/ipmi_watchdog.c: In function ‘ipmi_nmi’:
drivers/char/ipmi/ipmi_watchdog.c:1091: error: ‘NMI_HANDLED’ undeclared (first use in this function)
drivers/char/ipmi/ipmi_watchdog.c:1091: error: (Each undeclared identifier is reported only once
drivers/char/ipmi/ipmi_watchdog.c:1091: error: for each function it appears in.)
drivers/char/ipmi/ipmi_watchdog.c:1096: error: ‘NMI_DONE’ undeclared (first use in this function)
drivers/char/ipmi/ipmi_watchdog.c: In function ‘check_parms’:
drivers/char/ipmi/ipmi_watchdog.c:1280: error: implicit declaration of function ‘register_nmi_handler’
drivers/char/ipmi/ipmi_watchdog.c:1280: error: ‘NMI_UNKNOWN’ undeclared (first use in this function)
drivers/char/ipmi/ipmi_watchdog.c:1289: error: implicit declaration of function ‘unregister_nmi_handler’
drivers/char/ipmi/ipmi_watchdog.c: In function ‘ipmi_wdog_init’:
drivers/char/ipmi/ipmi_watchdog.c:1327: error: ‘NMI_UNKNOWN’ undeclared (first use in this function)
drivers/char/ipmi/ipmi_watchdog.c: In function ‘ipmi_wdog_exit’:
drivers/char/ipmi/ipmi_watchdog.c:1348: error: ‘NMI_UNKNOWN’ undeclared (first use in this function)
---
Index: linux-2.6/drivers/char/ipmi/ipmi_watchdog.c
===================================================================
--- linux-2.6.orig/drivers/char/ipmi/ipmi_watchdog.c
+++ linux-2.6/drivers/char/ipmi/ipmi_watchdog.c
@@ -65,6 +65,7 @@
* mechanism for it at that time.
*/
#include <asm/kdebug.h>
+#include <asm/nmi.h>
#define HAVE_DIE_NMI
#endif
next prev parent reply other threads:[~2011-10-03 15:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 19:06 [V7][PATCH 0/6] x86, nmi: new NMI handling routines Don Zickus
2011-09-30 19:06 ` [V7][PATCH 1/6] x86, nmi: split out nmi from traps.c Don Zickus
2011-09-30 19:06 ` [V7][PATCH 2/6] x86, nmi: create new NMI handler routines Don Zickus
2011-09-30 19:06 ` [V7][PATCH 3/6] x86, nmi: wire up NMI handlers to new routines Don Zickus
2011-09-30 19:06 ` [V7][PATCH 4/6] x86, nmi: add in logic to handle multiple events and unknown NMIs Don Zickus
2011-09-30 19:06 ` [V7][PATCH 5/6] x86, nmi: track NMI usage stats Don Zickus
2011-09-30 19:06 ` [V7][PATCH 6/6] x86, nmi: print out NMI stats in /proc/interrupts Don Zickus
2011-10-03 15:47 ` [V7][PATCH 0/6] x86, nmi: new NMI handling routines Peter Zijlstra
2011-10-03 15:52 ` Peter Zijlstra [this message]
2011-10-03 15:56 ` Don Zickus
2011-10-03 15:59 ` Peter Zijlstra
2011-10-04 15:05 ` Robert Richter
2011-10-04 16:43 ` Peter Zijlstra
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=1317657158.20367.30.camel@twins \
--to=peterz@infradead.org \
--cc=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=dzickus@redhat.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=robert.richter@amd.com \
--cc=x86@kernel.org \
--cc=ying.huang@intel.com \
/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