From: "Jan Beulich" <JBeulich@novell.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>, pasik@iki.fi
Cc: Bastian Blank <waldi@debian.org>,
James Harper <james.harper@bendigoit.com.au>,
xen-devel@lists.xensource.com,
Aleksi Suhonen <xen-devel-2010@ssd.axu.tm>
Subject: Re: Udev or XEN bug?
Date: Mon, 21 Jun 2010 15:52:55 +0100 [thread overview]
Message-ID: <4C1F98E70200007800007666@vpn.id2.novell.com> (raw)
In-Reply-To: <4C1F3966.3050804@goop.org>
>>> On 21.06.10 at 12:05, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Jan, do you have a patch which implements your suggestions?
Not for the pv-ops tree - in our tree, the fix logically belongs into the
2.6.22 up-merge of the Xen patches, but that wouldn't even come
close to applying to the pv-ops (or other newer) trees, due to other
subsequent infrastructure changes. I could try to put something
together, but that would be untested...
Jan
prev parent reply other threads:[~2010-06-21 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 16:50 Udev oder XEN bug? Stephan Seitz
2010-06-20 9:05 ` Udev or " Pasi Kärkkäinen
2010-06-20 12:14 ` Stephan Seitz
2010-06-21 10:05 ` Jeremy Fitzhardinge
2010-06-21 14:52 ` Jan Beulich [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=4C1F98E70200007800007666@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=james.harper@bendigoit.com.au \
--cc=jeremy@goop.org \
--cc=pasik@iki.fi \
--cc=waldi@debian.org \
--cc=xen-devel-2010@ssd.axu.tm \
--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).