From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Oleksandr Andrushchenko <andr2000@gmail.com>,
xen-devel@lists.xenproject.org
Subject: Re: Xen 4.9 Development Update
Date: Wed, 8 Feb 2017 13:17:12 -0500 [thread overview]
Message-ID: <20170208181711.GA32168@x230.dumpdata.com> (raw)
In-Reply-To: <b2d081c6-4cfd-b8b5-8794-c038d42b0b24@arm.com>
On Wed, Feb 08, 2017 at 06:03:00PM +0000, Julien Grall wrote:
> (CC Konrad)
>
> Hi Oleksandr,
>
> On 31/01/17 13:51, Oleksandr Andrushchenko wrote:
> >
> > On 01/30/2017 05:33 PM, Julien Grall wrote:
> > > This email only tracks big items for xen.git tree. Please reply for
> > > items you
> > > woulk like to see in 4.9 so that people have an idea what is going on and
> > > prioritise accordingly.
> > > == PV Drivers ==
> > >
> > > * Xen transport for 9pfs
> > > - Stefano Stabellini
> > >
> > > * PV calls
> > > - Stefano Stabellini
> > >
> > Are you considering other PV protocols for this drop? E.g.
> > multi-touch support, sound and display?
>
> That would be up to you and Konrad :).
I think we only have one left from Oleksandr. Two of them have been
reviewed by me today.
>
> Anyway, I am going to track any big inflight items even those not planned
> for next release. This will give us an overview of what's going on.
>
> What is the list of PV protocols you have in mind? And do you know who will
> work on it?
>
> Also, I should probably track separately the backend/frontend support if you
> plan to upstream them later.
>
> Cheers,
>
> --
> Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-02-08 18:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1cYDxP-0001LM-H5@lists.xenproject.org>
2017-01-31 13:51 ` Xen 4.9 Development Update Oleksandr Andrushchenko
2017-02-08 18:03 ` Julien Grall
2017-02-08 18:17 ` Konrad Rzeszutek Wilk [this message]
2017-02-08 18:56 ` Oleksandr Andrushchenko
2017-02-08 19:29 ` Julien Grall
2017-02-08 19:42 ` Oleksandr Andrushchenko
2017-02-08 19:27 ` Julien Grall
2017-02-08 18:59 ` Tamas K Lengyel
2017-02-15 21:40 ` Sergej Proskurin
2017-02-20 7:22 ` Haozhong Zhang
[not found] <E1csryw-0002dr-7q@lists.xenproject.org>
2017-03-30 18:24 ` Oleksandr Tyshchenko
2017-03-28 14:20 Julien Grall
[not found] <4c6084d167e041db9bc35dabe1e68c15@LASPEX02CAS01.citrite.net>
2017-01-30 16:21 ` Wei Liu
-- strict thread matches above, loose matches on Subject: below --
2017-01-30 15:33 Julien Grall
[not found] <E1cF0Mx-0005da-Th@lists.xenproject.org>
2016-12-08 15:20 ` Jan Beulich
2016-12-08 15:36 ` Wei Liu
2016-12-08 15:57 ` Jan Beulich
2016-12-08 16:00 ` Wei Liu
2016-12-08 15:12 Julien Grall
2016-12-08 22:00 ` Stefano Stabellini
2016-12-09 10:18 ` Julien Grall
2016-12-09 12:57 ` Oleksandr Andrushchenko
2016-12-09 13:57 ` Pasi Kärkkäinen
2016-12-09 14:10 ` Oleksandr Andrushchenko
2016-12-09 19:01 ` Stefano Stabellini
2016-12-09 19:09 ` Andrew Cooper
2017-01-26 12:27 ` Julien Grall
2017-01-26 17:06 ` Wei Liu
2017-01-30 15:32 ` Julien Grall
2017-01-30 15:45 ` Wei Liu
2017-02-08 17:53 ` Julien Grall
2016-12-14 13:45 ` Artem Mygaiev
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=20170208181711.GA32168@x230.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=andr2000@gmail.com \
--cc=julien.grall@arm.com \
--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 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.