From: Jeremy Fitzhardinge <jeremy@goop.org>
To: anthony.perard@citrix.com
Cc: xen-devel@lists.xensource.com, Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH] Wait the state Connect of the frontend before connect the backend.
Date: Thu, 20 May 2010 14:24:52 -0700 [thread overview]
Message-ID: <4BF5A8A4.2050809@goop.org> (raw)
In-Reply-To: <1274116684-6349-1-git-send-email-anthony.perard@citrix.com>
On 05/17/2010 10:18 AM, anthony.perard@citrix.com wrote:
> From: Anthony PERARD <anthony.perard@citrix.com>
>
> The frontend of the framebuffer set a value (request-abs-pointer) and go
> to the state Connected. The backend must read this value only when the
> frontend has the state Connected.
>
This works well. It should go into git.
(Anthony: you'll need to append a "Signed-off-by:" line to be strictly
complete.)
Tested-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
J
> ---
> hw/xen_backend.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/hw/xen_backend.c b/hw/xen_backend.c
> index 76d07ec..31ed7b0 100644
> --- a/hw/xen_backend.c
> +++ b/hw/xen_backend.c
> @@ -411,8 +411,7 @@ static int xen_be_try_connect(struct XenDevice *xendev)
> {
> int rc = 0;
>
> - if (xendev->fe_state != XenbusStateInitialised &&
> - xendev->fe_state != XenbusStateConnected) {
> + if (xendev->fe_state != XenbusStateConnected) {
> if (xendev->ops->flags & DEVOPS_FLAG_IGNORE_STATE) {
> xen_be_printf(xendev, 2, "frontend not ready, ignoring\n");
> } else {
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
next prev parent reply other threads:[~2010-05-20 21:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 17:18 [PATCH] Wait the state Connect of the frontend before connect the backend anthony.perard
2010-05-17 17:56 ` Jeremy Fitzhardinge
2010-05-20 21:24 ` Jeremy Fitzhardinge [this message]
2010-05-21 15:23 ` [PATCH] Wait the state Connect of the frontend before connect the backend. [and 1 more messages] Ian Jackson
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=4BF5A8A4.2050809@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Jackson@eu.citrix.com \
--cc=anthony.perard@citrix.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.