All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Jan Beulich <JBeulich@novell.com>
Subject: Re: Xen watchdog patch disposition?
Date: Thu, 27 Jan 2011 08:54:10 -0800	[thread overview]
Message-ID: <4D41A332.80005@goop.org> (raw)
In-Reply-To: <20110127145003.GB3282@dumpdata.com>

On 01/27/2011 06:50 AM, Konrad Rzeszutek Wilk wrote:
> On Thu, Jan 27, 2011 at 12:50:51PM +0000, Jan Beulich wrote:
>> Jeremy,
>>
>> while originally I had hoped this patch, sitting in xen/next, would get
>> pushed for .37, that didn't happen and now the .38 merge window
>> was missed too. Trying to get this to Linux on my own seems
>> inappropriate, so can I hope that you will include this with whatever
> Why would it be inappropiate? It looks as if the maintainer
> for the watchdog subsystems is linux-watchdog@vger.kernel.org 
>
> Are they not responding to the patch?

AKPM is also generally the maintainer of last resort for these kinds of
little subsystems if there's no formal maintainer (or the listed
maintainer is non-responsive).

    J

  parent reply	other threads:[~2011-01-27 16:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27 12:50 Xen watchdog patch disposition? Jan Beulich
2011-01-27 14:50 ` Konrad Rzeszutek Wilk
2011-01-27 15:09   ` Jan Beulich
2011-01-27 15:23     ` Ian Campbell
2011-01-27 15:40     ` Konrad Rzeszutek Wilk
2011-01-27 15:52       ` Jan Beulich
2011-01-27 16:54   ` Jeremy Fitzhardinge [this message]
2011-01-27 16:57 ` Jeremy Fitzhardinge

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=4D41A332.80005@goop.org \
    --to=jeremy@goop.org \
    --cc=JBeulich@novell.com \
    --cc=konrad.wilk@oracle.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.