[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <547DD64602000078000C2DC0@mail.emea.novell.com>
Date: Tue, 02 Dec 2014 15:09:58 +0000
From: "Jan Beulich" <jbeulich@...e.com>
To: <konrad.wilk@...cle.com>
Cc: <linux@...elenboom.it>, <bhelgaas@...gle.com>,
<xen-devel@...ts.xenproject.org>, <linux-kernel@...r.kernel.org>,
<linux-pci@...r.kernel.org>
Subject: Re: [Xen-devel] [PATCH v4] Fixes for PCI backend for 3.19
>>> Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> 12/02/14 4:05 PM >>>
>On Tue, Dec 02, 2014 at 10:10:11AM +0000, Jan Beulich wrote:
>> >>> On 21.11.14 at 23:17, <konrad.wilk@...cle.com> wrote:
>> > Konrad Rzeszutek Wilk (7):
>> > xen/pciback: Don't deadlock when unbinding.
>> > driver core: Provide an wrapper around the mutex to do lockdep warnings
>> > xen/pciback: Include the domain id if removing the device whilst still in use
>> > xen/pciback: Print out the domain owning the device.
>> > xen/pciback: Remove tons of dereferences
>> > PCI: Expose pci_load_saved_state for public consumption.
>> > xen/pciback: Restore configuration space when detaching from a guest.
>>
>> So my "xen-pciback: drop SR-IOV VFs when PF driver unloads" isn't
>> among them, nor is there any alternative. What's the status of that
>> patch (or the problem that prompted its creation)?
>
>Oh, I've it in my queue. Um, here is what I did to it - I hadn't
>yet tested it - hence the reason it is not on that list.
Yeah, if you like it better that way, it looks okay to me now.
Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists