On Thu, 17 Jul 2014, Andrew Duggan wrote:
> It is possible that the hid-rmi driver could get loaded onto a device which
> does not have the
> expected report ids. This should not happen because it would indicate that
> the hid-rmi driver is
> not compatible with that device. However, if it does
On Thu, 17 Jul 2014, Andrew Duggan wrote:
It is possible that the hid-rmi driver could get loaded onto a device which
does not have the
expected report ids. This should not happen because it would indicate that
the hid-rmi driver is
not compatible with that device. However, if it does
On Jul 17 2014 or thereabouts, Andrew Duggan wrote:
> It is possible that the hid-rmi driver could get loaded onto a device which
> does not have the
> expected report ids. This should not happen because it would indicate that
> the hid-rmi driver is
> not compatible with that device. However,
On Jul 17 2014 or thereabouts, Andrew Duggan wrote:
It is possible that the hid-rmi driver could get loaded onto a device which
does not have the
expected report ids. This should not happen because it would indicate that
the hid-rmi driver is
not compatible with that device. However, if it
It is possible that the hid-rmi driver could get loaded onto a device which
does not have the
expected report ids. This should not happen because it would indicate that the
hid-rmi driver is
not compatible with that device. However, if it does happen it should return an
error from probe
instead
It is possible that the hid-rmi driver could get loaded onto a device which
does not have the
expected report ids. This should not happen because it would indicate that the
hid-rmi driver is
not compatible with that device. However, if it does happen it should return an
error from probe
instead
6 matches
Mail list logo