staging: unisys: Do not use 0 as the default bus root device number
authorDon Zickus <dzickus@redhat.com>
Thu, 4 Jun 2015 13:22:40 +0000 (09:22 -0400)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 8 Jun 2015 20:36:43 +0000 (13:36 -0700)
commit65bd6e4607a19eafbf0d23ce184b6cefc19e317d
tree24dd128a7a18e09cc1101562c0396af243e60cf7
parentee983d902ecea8d1d524f3f2505b89a315555abe
staging: unisys: Do not use 0 as the default bus root device number

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 consistently.  Fix visorbus.h to use u32 there.  Fix
the resulting printk warning too.

Signed-off-by: Don Zickus <dzickus@redhat.com>
Signed-off-by: Benjamin Romer <benjamin.romer@unisys.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/staging/unisys/include/visorbus.h
drivers/staging/unisys/visorbus/visorbus_main.c
drivers/staging/unisys/visorbus/visorchipset.c