From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Xen watchdog patch disposition?
Date: Thu, 27 Jan 2011 08:57:58 -0800
Message-ID: <4D41A416.9060604@goop.org>
References: <4D41783B020000780002EC64@vpn.id2.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4D41783B020000780002EC64@vpn.id2.novell.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On 01/27/2011 04:50 AM, Jan Beulich wrote:
> 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,

It's perfectly appropriate.  I can Ack it if that makes you feel better.

If it were more core Xen code I'd want to be more involved in it, but
the "Xen implementation of some subsystem driver" is pretty fair game
for anyone.  For example, I'd have no objections to someone posting
pv(scsi|usb) front/backends as an independent effort (at least in
principle; in practice I might have objections to the patch contents
themselves).

    J