From: "Jan Beulich" <JBeulich@suse.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
StefanoStabellini <Stefano.Stabellini@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"G.R." <firemeteor@users.sourceforge.net>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH v2] qemu-xen:Correctly expose PCH ISA bridge for IGD passthrough [and 2 more messages]
Date: Fri, 10 May 2013 11:35:20 +0100 [thread overview]
Message-ID: <518CE98802000078000D5150@nat28.tlf.novell.com> (raw)
In-Reply-To: <518CC758.10002@eu.citrix.com>
>>> On 10.05.13 at 12:09, George Dunlap <george.dunlap@eu.citrix.com> wrote:
> But if he were going to pick it up, or if he wants to go work with the
> submitter, who may not have a clear understanding what the delay was
> about or how the development process works, then he'd first need to
> figure out what the status was, right?
But that's what is available in the list archives - in the case at hand,
Pasi pointed at patches that had trees of subsequent communication
attached to them, and in all cases the leaves where unanswered
questions. So figuring out the status was quite strait forward here.
I admit that this may not always be as simple (or otherwise I likely
wouldn't even have bothered looking at the old conversation again).
Bottom line is that I think we should be allowed to expect homework
to be done before pinging maintainers.
Jan
next prev parent reply other threads:[~2013-05-10 10:35 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 16:12 Patch series for IGD passthrough Rui Guo
2013-02-07 16:12 ` [PATCH 1/3] qemu-xen-trad/pt_msi_disable: do not clear all MSI flags Rui Guo
2013-02-07 16:12 ` [PATCH 2/3] qemu-xen-trad: Correctly expose PCH ISA bridge for IGD passthrough Rui Guo
2013-02-07 16:30 ` Jan Beulich
2013-02-07 17:43 ` G.R.
2013-02-08 7:51 ` Jan Beulich
2013-05-21 15:39 ` G.R.
2013-05-24 4:02 ` G.R.
2013-02-08 11:30 ` Stefano Stabellini
2013-02-08 11:36 ` Jan Beulich
2013-02-08 11:48 ` Stefano Stabellini
2013-05-21 15:52 ` G.R.
2013-05-21 15:57 ` Jan Beulich
2013-02-07 16:12 ` [PATCH 3/3] qemu-xen-trad: IGD passthrough: Expose vendor specific pci cap on host bridge Rui Guo
2013-02-07 16:40 ` Jan Beulich
2013-02-07 17:38 ` G.R.
2013-02-08 7:56 ` Jan Beulich
2013-06-19 10:37 ` G.R.
2013-06-21 18:03 ` Konrad Rzeszutek Wilk
2013-06-25 14:08 ` Ross Philipson
2013-06-25 14:54 ` Konrad Rzeszutek Wilk
2013-06-25 15:01 ` Ross Philipson
2013-06-26 4:18 ` G.R.
2013-06-26 12:53 ` Konrad Rzeszutek Wilk
2013-06-26 17:26 ` Ross Philipson
2013-06-27 7:27 ` G.R.
2013-07-01 13:06 ` Konrad Rzeszutek Wilk
2013-07-15 16:06 ` Pasi Kärkkäinen
2013-07-15 17:47 ` Ross Philipson
2013-07-15 22:55 ` Pasi Kärkkäinen
2013-08-05 16:15 ` Pasi Kärkkäinen
2013-08-06 3:44 ` G.R.
2013-09-25 14:28 ` Pasi Kärkkäinen
2014-08-20 15:20 ` Pasi Kärkkäinen
2013-06-25 14:26 ` G.R.
2013-02-08 11:14 ` Patch series for IGD passthrough Stefano Stabellini
2013-03-20 17:17 ` Pasi Kärkkäinen
2013-04-15 20:48 ` Pasi Kärkkäinen
2013-04-16 10:56 ` George Dunlap
2013-04-16 15:59 ` Pasi Kärkkäinen
2013-04-18 11:48 ` Stefano Stabellini
2012-12-19 13:06 ` [PATCH v2] qemu-xen:Correctly expose PCH ISA bridge " G.R.
2012-12-20 13:13 ` Stefano Stabellini
2013-02-22 18:05 ` Ian Jackson
2013-02-25 10:10 ` Jan Beulich
2013-02-25 11:24 ` Ian Jackson
2013-02-25 11:29 ` Jan Beulich
2013-02-25 12:49 ` Stefano Stabellini
2013-05-07 17:12 ` [PATCH v2] qemu-xen:Correctly expose PCH ISA bridge for IGD passthrough [and 2 more messages] Ian Jackson
2013-05-09 13:17 ` Pasi Kärkkäinen
2013-05-10 9:12 ` Jan Beulich
2013-05-10 9:40 ` Pasi Kärkkäinen
2013-05-10 10:00 ` Ian Campbell
2013-05-10 10:09 ` George Dunlap
2013-05-10 10:33 ` Ian Campbell
2013-05-10 10:44 ` Pasi Kärkkäinen
2013-05-10 10:35 ` Jan Beulich [this message]
2013-02-25 16:46 ` [PATCH v2] qemu-xen:Correctly expose PCH ISA bridge for IGD passthrough Ian Jackson
2013-04-18 11:47 ` Patch series " Stefano Stabellini
2013-05-03 15:14 ` Pasi Kärkkäinen
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=518CE98802000078000D5150@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=firemeteor@users.sourceforge.net \
--cc=george.dunlap@eu.citrix.com \
--cc=xen-devel@lists.xen.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.