From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Oleksandr Andrushchenko <andr2000@gmail.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, airlied@linux.ie,
daniel.vetter@intel.com, seanpaul@chromium.org,
gustavo@padovan.org, jgross@suse.com, konrad.wilk@oracle.com
Cc: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: Re: [PATCH v3] drm/xen-front: Add support for Xen PV display frontend
Date: Wed, 21 Mar 2018 21:14:28 -0400 [thread overview]
Message-ID: <d7cd6147-da9f-0f18-cb05-4dccbf212255@oracle.com> (raw)
In-Reply-To: <1521644293-14612-2-git-send-email-andr2000@gmail.com>
On 03/21/2018 10:58 AM, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
>
> Add support for Xen para-virtualized frontend display driver.
> Accompanying backend [1] is implemented as a user-space application
> and its helper library [2], capable of running as a Weston client
> or DRM master.
> Configuration of both backend and frontend is done via
> Xen guest domain configuration options [3].
I won't claim that I really understand what's going on here as far as
DRM stuff is concerned but I didn't see any obvious issues with Xen bits.
So for that you can tack on my
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
next prev parent reply other threads:[~2018-03-22 1:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 14:58 [PATCH v3] drm/xen-front: Add support for Xen PV display frontend Oleksandr Andrushchenko
2018-03-21 14:58 ` Oleksandr Andrushchenko
2018-03-22 1:14 ` Boris Ostrovsky [this message]
2018-03-22 9:36 ` Oleksandr Andrushchenko
2018-03-22 7:56 ` Daniel Vetter
2018-03-23 15:54 ` Oleksandr Andrushchenko
2018-03-26 8:18 ` Daniel Vetter
2018-03-26 12:46 ` Oleksandr Andrushchenko
2018-03-27 9:34 ` Oleksandr Andrushchenko
2018-03-27 9:50 ` Daniel Vetter
2018-03-27 10:08 ` Oleksandr Andrushchenko
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=d7cd6147-da9f-0f18-cb05-4dccbf212255@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=airlied@linux.ie \
--cc=andr2000@gmail.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_andrushchenko@epam.com \
--cc=seanpaul@chromium.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).