From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-watchdog@vger.kernel.org,
Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Campbell <ian.campbell@citrix.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: [Xen-devel] [PATCH, resend] Xen watchdog driver
Date: Mon, 14 Feb 2011 15:19:24 -0500 [thread overview]
Message-ID: <20110214201924.GA17726@dumpdata.com> (raw)
In-Reply-To: <20110214200837.GB3790@infomag.iguana.be>
On Mon, Feb 14, 2011 at 09:08:37PM +0100, Wim Van Sebroeck wrote:
> Hi All,
>
> > On Thu, Jan 27, 2011 at 03:42:48PM +0000, Jan Beulich wrote:
> > > While the hypervisor change adding SCHEDOP_watchdog support included a
> > > daemon to make use of the new functionality, having a kernel driver
> > > for /dev/watchdog so that user space code doesn't need to distinguish
> > > non-Xen and Xen seems to be preferable.
> >
> > Hey Andrew,
> > I was wondering if you could help us out. Jan posted this patch
> > way back in Sep, then again in Oct on the xen-watchdog mailing list
> > with with no responses except Ian's Ack and my Reviewed-by. Would you
> > be OK taking this patch under your wing or do you think I ought to
> > send a git pull to Linus during the 2.6.39 merge window directly?
> I
> 'm completing review of 2 other drivers first.
> Then I will review this one and add it to linux-2.5-watchdog-next for broader testing.
Excellent. Thank you!
prev parent reply other threads:[~2011-02-14 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 15:42 [PATCH, resend] Xen watchdog driver Jan Beulich
2011-02-14 14:56 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-02-14 20:07 ` Andrew Morton
2011-02-14 20:08 ` Wim Van Sebroeck
2011-02-14 20:19 ` Konrad Rzeszutek Wilk [this message]
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=20110214201924.GA17726@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@novell.com \
--cc=akpm@linux-foundation.org \
--cc=ian.campbell@citrix.com \
--cc=jeremy@goop.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@iguana.be \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).