From: John Haxby <john.haxby@oracle.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: [Qemu-devel] Re: [PATCH 1 of 2] Introduce a new 'connected' xendev op called when Connected.
Date: Fri, 11 Mar 2011 13:15:43 +0000 [thread overview]
Message-ID: <4D7A207F.8080507@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1008271543250.2545@kaball-desktop>
It's been something over six months since this patch was submitted
(actually it was resend because the first version didn't say "PATCH" in
the subject. So far as I can tell it's not made it into qemu git
(hw/xen_backend.h, for example, doesn't show the extra field in struct
XenDevOps).
This problem came up again on the xen-devel lists today and it's a shame
that there's been a patch out there since last summer that people are
now having to re-discover and re-patch :-(
jch
On 27/08/10 15:43, Stefano Stabellini wrote:
> From: John Haxby <john.haxby@oracle.com>
>
> Introduce a new 'connected' xendev op called when Connected.
>
> Rename the existing xendev 'connect' op to 'initialised' and introduce
> a new 'connected' op. This new op, if defined, is called when the
> backend is connected. Note that since there is no state transition this
> may be called more than once.
>
> Signed-off-by: John Haxby <john.haxby@oracle.com>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
>
[snip]
prev parent reply other threads:[~2011-03-11 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 14:43 [Qemu-devel] [PATCH 1 of 2] Introduce a new 'connected' xendev op called when Connected Stefano Stabellini
2011-03-11 13:15 ` John Haxby [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=4D7A207F.8080507@oracle.com \
--to=john.haxby@oracle.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=qemu-devel@nongnu.org \
/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).