From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Bjorn Helgaas <bhelgaas@google.com>, ian.campbell@citrix.com
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
xen-devel <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] xen/pci: Deal with toolstack missing an 'XenbusStateClosing'.
Date: Mon, 4 Nov 2013 15:43:04 -0500 [thread overview]
Message-ID: <20131104204304.GA18492@phenom.dumpdata.com> (raw)
In-Reply-To: <CAErSpo7zw3MSNzdjRcZuy44uOGT_GZ8T4vaqgkd1fvWG4fadTA@mail.gmail.com>
> Sure; this is your baby :) Why don't you handle it via your tree,
> since it's more related to xen than any PCI core stuff.
>
> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Definitly fixed in v3.12. Just tested it and it works.
George, Ian, how do I "close" a bug in http://bugs.xenproject.org/xen/bug/12 ?
prev parent reply other threads:[~2013-11-04 20:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130610202456.GA17822@phenom.dumpdata.com>
[not found] ` <1370898399-20968-1-git-send-email-konrad.wilk@oracle.com>
2013-06-10 21:06 ` [PATCH] xen/pci: Deal with toolstack missing an 'XenbusStateClosing' Konrad Rzeszutek Wilk
2013-06-11 7:29 ` [Xen-devel] " Jan Beulich
2013-06-11 9:00 ` George Dunlap
2013-06-11 13:03 ` konrad wilk
2013-06-11 15:36 ` George Dunlap
2013-06-11 16:08 ` konrad wilk
2013-06-11 16:17 ` George Dunlap
2013-06-11 16:24 ` konrad wilk
2013-06-12 13:45 ` Konrad Rzeszutek Wilk
2013-06-12 13:47 ` George Dunlap
2013-06-12 14:27 ` Konrad Rzeszutek Wilk
2013-06-12 17:28 ` Bjorn Helgaas
2013-06-14 16:28 ` Konrad Rzeszutek Wilk
2013-11-04 20:43 ` Konrad Rzeszutek Wilk [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=20131104204304.GA18492@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=bhelgaas@google.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xensource.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).