All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen watchdog patch disposition?
Date: Thu, 27 Jan 2011 08:57:58 -0800	[thread overview]
Message-ID: <4D41A416.9060604@goop.org> (raw)
In-Reply-To: <4D41783B020000780002EC64@vpn.id2.novell.com>

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

      parent reply	other threads:[~2011-01-27 16:57 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
2011-01-27 16:57 ` Jeremy Fitzhardinge [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=4D41A416.9060604@goop.org \
    --to=jeremy@goop.org \
    --cc=JBeulich@novell.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.