All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <keir@xen.org>
Subject: Re: Re: Konrad devel/next-3.0, pci-passthrough not working: Error: pci: PCI Backend and pci-stub don't own device
Date: Mon, 27 Jun 2011 11:26:12 -0400	[thread overview]
Message-ID: <20110627152612.GI6978@dumpdata.com> (raw)
In-Reply-To: <59650171.20110622171741@eikelenboom.it>

> It does the trick, pci-passthrough works again with this patch !

Excellent. Let me repost the patchset with some modification (move the whole driver to drivers/xen)
and get some folks to review it.
> 
> Currently testing your "master branch (3.0-rc4)"  with the "devel/acpi-cpufreq" patches pulled it, together with this pciback patch.
> 
> Seems to be working OK, thx again !

Great!

  reply	other threads:[~2011-06-27 15:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21 13:41 Konrad devel/next-3.0, pci-passthrough not working: Error: pci: PCI Backend and pci-stub don't own device Sander Eikelenboom
2011-06-21 14:13 ` Konrad Rzeszutek Wilk
2011-06-21 14:24   ` Sander Eikelenboom
2011-06-21 14:40   ` Sander Eikelenboom
2011-06-21 15:11   ` Sander Eikelenboom
2011-06-21 15:39     ` Sander Eikelenboom
2011-06-21 17:05     ` Konrad Rzeszutek Wilk
2011-06-21 17:17       ` Sander Eikelenboom
2011-06-21 19:02       ` Sander Eikelenboom
2011-06-22 14:00         ` Konrad Rzeszutek Wilk
2011-06-22 14:13           ` Sander Eikelenboom
2011-06-22 14:28             ` Konrad Rzeszutek Wilk
2011-06-22 15:17               ` Sander Eikelenboom
2011-06-27 15:26                 ` Konrad Rzeszutek Wilk [this message]
2011-06-27 17:09                   ` Sander Eikelenboom
2011-06-29  7:19               ` Ian Campbell

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=20110627152612.GI6978@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=keir@xen.org \
    --cc=linux@eikelenboom.it \
    --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 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.