From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Sucheta Chakraborty <sucheta.chakraborty@qlogic.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
zhenzhong.duan@oracle.com, Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.4 development update: Feature freeze has started
Date: Tue, 12 Nov 2013 09:17:21 -0500 [thread overview]
Message-ID: <20131112141721.GA9306@phenom.dumpdata.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1311121201280.26077@kaball.uk.xensource.com>
On Tue, Nov 12, 2013 at 12:04:29PM +0000, Stefano Stabellini wrote:
> On Tue, 12 Nov 2013, Jan Beulich wrote:
> > >>> On 11.11.13 at 19:03, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > >> == Open ==
> > >>
> > >> * qemu-upstream not freeing pirq
> > >> > http://www.gossamer-threads.com/lists/xen/devel/281498
> > >> status: patches posted, tested-and-acked
> > >
> > > .. but not yet committed. Ian Jackson is the person to do it right?
This is the one I was thinking off:
http://lists.xen.org/archives/html/xen-devel/2013-07/msg00004.html
which ..
> >
> > No, qemu-upstream is Stefano's playgound.
>
> Although the patch has been reworked for upstream QEMU
> (http://marc.info/?l=xen-devel&m=137265766424502), it was only build
> tested. Considering that I don't have the hardware to test it right now
> and that it's not obviously correct, I was waiting for Zhenzhong to come
> back and let me know if it is actually behaving as expected.
.. I presume is blocked until Stefano has an Tested-by from either
Sucheta (Qlogic) or Duan.
CC-ing them both.
next prev parent reply other threads:[~2013-11-12 14:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 17:18 Xen 4.4 development update: Feature freeze has started George Dunlap
2013-11-11 17:32 ` Andrew Cooper
2013-11-15 14:36 ` George Dunlap
2013-11-15 14:44 ` Jan Beulich
2013-11-15 14:48 ` Andrew Cooper
2013-11-15 14:52 ` Andrew Cooper
2013-11-11 18:03 ` Konrad Rzeszutek Wilk
2013-11-12 8:55 ` Jan Beulich
2013-11-12 12:04 ` Stefano Stabellini
2013-11-12 14:17 ` Konrad Rzeszutek Wilk [this message]
2013-11-12 9:24 ` Ian Campbell
2013-11-11 20:49 ` Boris Ostrovsky
2013-11-11 21:02 ` Ben Guthro
2013-11-12 10:54 ` David Vrabel
2013-11-12 11:09 ` Ian Campbell
2013-11-12 11:11 ` Roger Pau Monné
2013-11-15 15:37 ` George Dunlap
2013-11-15 15:51 ` Roger Pau Monné
2013-11-12 11:20 ` Wei Liu
2013-11-12 11:53 ` Fabio Fantoni
2013-11-12 12:49 ` Stefano Stabellini
2013-11-12 14:20 ` Konrad Rzeszutek Wilk
2013-11-12 14:22 ` Ian Campbell
2013-11-12 14:26 ` Wei Liu
2013-11-12 15:07 ` Konrad Rzeszutek Wilk
2013-11-12 15:16 ` Wei Liu
2013-11-15 16:11 ` George Dunlap
2013-11-15 16:28 ` George Dunlap
2013-11-19 10:47 ` Ian Campbell
2013-11-14 9:28 ` Dario Faggioli
2013-11-14 14:16 ` Nate Studer
2013-11-14 22:20 ` Dario Faggioli
2013-11-15 9:03 ` Jan Beulich
2013-11-15 9:41 ` Dario Faggioli
2013-11-15 9:00 ` Jan Beulich
2013-11-14 9:38 ` Dario Faggioli
2013-11-14 13:42 ` Elena Ufimtseva
2013-11-15 16:34 ` George Dunlap
2013-11-15 18:07 ` Dario Faggioli
2013-11-15 20:39 ` Shriram Rajagopalan
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=20131112141721.GA9306@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=sucheta.chakraborty@qlogic.com \
--cc=xen-devel@lists.xen.org \
--cc=zhenzhong.duan@oracle.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 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).