linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Juergen Gross <jgross@suse.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
	linux-fbdev@vger.kernel.org, boris.ostrovsky@oracle.com,
	stable@vger.kernel.org
Subject: Re: [PATCH] xen, fbfront: fix connecting to backend
Date: Wed, 05 Apr 2017 14:28:31 +0000	[thread overview]
Message-ID: <5998137.VJ3GrqTG96@amdc3058> (raw)
In-Reply-To: <3226cec6-8f68-6d15-4427-eb8f2d1944a1@suse.com>


Hi,

On Wednesday, April 05, 2017 10:18:21 AM Juergen Gross wrote:
> On 23/03/17 13:52, Juergen Gross wrote:
> > Connecting to the backend isn't working reliably in xen-fbfront: in
> > case XenbusStateInitWait of the backend has been missed the backend
> > transition to XenbusStateConnected will trigger the connected state
> > only without doing the actions required when the backend has
> > connected.
> > 
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Juergen Gross <jgross@suse.com>
> 
> Bartlomiej, any comments? Can you please take this patch or should I
> carry it through the Xen tree?

Looks fine to me, I will queue it for 4.11 on Friday.

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics


      reply	other threads:[~2017-04-05 14:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 12:52 [PATCH] xen, fbfront: fix connecting to backend Juergen Gross
2017-03-23 13:37 ` [Xen-devel] " Jan Beulich
     [not found] ` <58D3DDB40200007800146C6B@suse.com>
2017-03-23 13:56   ` Juergen Gross
2017-03-23 14:21     ` Jan Beulich
2017-03-23 14:11 ` Boris Ostrovsky
2017-04-07 15:27   ` Bartlomiej Zolnierkiewicz
2017-04-05  8:18 ` Juergen Gross
2017-04-05 14:28   ` Bartlomiej Zolnierkiewicz [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=5998137.VJ3GrqTG96@amdc3058 \
    --to=b.zolnierkie@samsung.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=xen-devel@lists.xenproject.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).