From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Xen watchdog patch disposition? Date: Thu, 27 Jan 2011 08:54:10 -0800 Message-ID: <4D41A332.80005@goop.org> References: <4D41783B020000780002EC64@vpn.id2.novell.com> <20110127145003.GB3282@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20110127145003.GB3282@dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: "xen-devel@lists.xensource.com" , Jan Beulich List-Id: xen-devel@lists.xenproject.org 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