On 10/31/2013 01:23 PM, Michal Privoznik wrote:
> If a PCI deivce is not binded to any driver (e.g. there's yet no PCI
> driver in the linux kernel) but still users want to passthru the device
> we fail the whole operation as we fail to resolve the 'driver' link
> under the PCI device sysfs tree. O
On Tue, Nov 05, 2013 at 07:59:32AM +0100, Claudio Bley wrote:
> At Mon, 4 Nov 2013 15:59:18 +0100,
> Martin Kletzander wrote:
> >
> > On Thu, Oct 31, 2013 at 11:23:41AM +, Michal Privoznik wrote:
> >
> > s/not binded/unbinded/ in $SUBJ
>
> s/unbinded/unbound/
>
> Somebody else with a _guess
At Mon, 4 Nov 2013 15:59:18 +0100,
Martin Kletzander wrote:
>
> On Thu, Oct 31, 2013 at 11:23:41AM +, Michal Privoznik wrote:
>
> s/not binded/unbinded/ in $SUBJ
s/unbinded/unbound/
Somebody else with a _guess_? :-)
--
AV-Test GmbH, Henricistraße 20, 04155 Leipzig, Germany
Phone: +49 341 2
On Thu, Oct 31, 2013 at 11:23:41AM +, Michal Privoznik wrote:
s/not binded/unbinded/ in $SUBJ
> If a PCI deivce is not binded to any driver (e.g. there's yet no PCI
> driver in the linux kernel) but still users want to passthru the device
> we fail the whole operation as we fail to resolve th
If a PCI deivce is not binded to any driver (e.g. there's yet no PCI
driver in the linux kernel) but still users want to passthru the device
we fail the whole operation as we fail to resolve the 'driver' link
under the PCI device sysfs tree. Obviously, this is not a fatal error
and it shouldn't be
