From: Don Zickus <dzickus@redhat.com>
To: <x86@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
thomas.mingarelli@hp.com, Don Zickus <dzickus@redhat.com>
Subject: [PATCH 0/3] x86, nmi: Fixes
Date: Thu, 29 Mar 2012 16:11:14 -0400 [thread overview]
Message-ID: <1333051877-15755-1-git-send-email-dzickus@redhat.com> (raw)
The patch series started with fixes for kmemcheck but slowly involved
the fixing hpwdt. Hopefully everything is ok for now.
Don Zickus (2):
watchdog, hpwdt: Remove priority option for NMI callback
x86, nmi: Add new NMI queues to deal with IO_CHK and SERR
Li Zhong (1):
x86,nmi: Fix page faults by nmiaction if kmemcheck is enabled
arch/x86/include/asm/nmi.h | 22 ++++++++++-
arch/x86/kernel/nmi.c | 83 +++++++++++++-------------------------------
drivers/watchdog/hpwdt.c | 46 +++++++++++++------------
3 files changed, 68 insertions(+), 83 deletions(-)
--
1.7.7.6
next reply other threads:[~2012-03-29 20:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 20:11 Don Zickus [this message]
2012-03-29 20:11 ` [PATCH 1/3] watchdog, hpwdt: Remove priority option for NMI callback Don Zickus
2012-04-25 13:54 ` [tip:core/locking] " tip-bot for Don Zickus
2012-04-26 7:13 ` Wim Van Sebroeck
2012-04-26 12:26 ` Don Zickus
2012-04-26 13:47 ` Mingarelli, Thomas
2012-04-26 13:53 ` Wim Van Sebroeck
2012-03-29 20:11 ` [PATCH 2/3] x86, nmi: Add new NMI queues to deal with IO_CHK and SERR Don Zickus
2012-04-25 13:55 ` [tip:core/locking] x86/nmi: " tip-bot for Don Zickus
2012-03-29 20:11 ` [PATCH 3/3] x86,nmi: Fix page faults by nmiaction if kmemcheck is enabled Don Zickus
2012-04-25 13:55 ` [tip:core/locking] x86/nmi: " tip-bot for Li Zhong
2012-04-20 16:17 ` [PATCH 0/3] x86, nmi: Fixes Seiji Aguchi
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=1333051877-15755-1-git-send-email-dzickus@redhat.com \
--to=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=thomas.mingarelli@hp.com \
--cc=x86@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
Powered by JetHome