From: Wim Van Sebroeck <wim@iguana.be>
To: "Mingarelli, Thomas" <Thomas.Mingarelli@hp.com>
Cc: Don Zickus <dzickus@redhat.com>,
"mingo@kernel.org" <mingo@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>
Subject: Re: [tip:core/locking] watchdog, hpwdt: Remove priority option for NMI callback
Date: Thu, 26 Apr 2012 15:53:01 +0200 [thread overview]
Message-ID: <20120426135301.GK6553@spo001.leaseweb.com> (raw)
In-Reply-To: <9774516974AF5F4C8A2C3C69CD341233203A83B5@G9W0755.americas.hpqcorp.net>
Hi All,
> Wim:
>
>
> Don is correct. We did have a separate discussion about this after I denied the original patch. It is all good now.
>
> And thanks for cutting in the port 0x72 patch.
>
> Thanks,
> Tom
Then this is also OK for me.
You can add an Acked-by me :-).
Kind regards,
Wim.
next prev parent reply other threads:[~2012-04-26 14:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 20:11 [PATCH 0/3] x86, nmi: Fixes Don Zickus
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 [this message]
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=20120426135301.GK6553@spo001.leaseweb.com \
--to=wim@iguana.be \
--cc=Thomas.Mingarelli@hp.com \
--cc=akpm@linux-foundation.org \
--cc=dzickus@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®