On Fri, Jun 05, 2015 at 06:04:14PM +0300, Dan Carpenter wrote:
> Sorry, I should have read on the later patches. That sounds fine.
Hi Dan,
No worries. I will take the blame for that. I should have communicated
that or done a better job making less confusing. :-(
Cheers,
Don
__
Sorry, I should have read on the later patches. That sounds fine.
regards,
dan carpenter
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
On Thu, Jun 04, 2015 at 05:19:44PM +0300, Dan Carpenter wrote:
> On Thu, Jun 04, 2015 at 09:22:40AM -0400, Benjamin Romer wrote:
> > diff --git a/drivers/staging/unisys/visorbus/visorchipset.c
> > b/drivers/staging/unisys/visorbus/visorchipset.c
> > index 4dd0a07..618732b 100644
> > --- a/drivers/
On Thu, Jun 04, 2015 at 09:22:40AM -0400, Benjamin Romer wrote:
> diff --git a/drivers/staging/unisys/visorbus/visorchipset.c
> b/drivers/staging/unisys/visorbus/visorchipset.c
> index 4dd0a07..618732b 100644
> --- a/drivers/staging/unisys/visorbus/visorchipset.c
> +++ b/drivers/staging/unisys/vis
From: Don Zickus
I used 0 as the device id for the bus root, neglecting the fact that
device 0 is a valid id in Unisys's configuration. Modify this to
use UINT_MAX instead as a unique number.
As fallout from this change it was noticed the bus_no and dev_no was not
defined the same way consisten