staging: unisys: Do not use 0 as the default bus root device number

Browse source

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>

...

This commit is contained in:

Don Zickus 2015-06-04 09:22:40 -04:00 • committed by Greg Kroah-Hartman

parent ee983d902e

commit 65bd6e4607

3 changed files with 7 additions and 5 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

4

drivers/staging/unisys/include/visorbus.h

View file

2

drivers/staging/unisys/visorbus/visorbus_main.c

View file

6

drivers/staging/unisys/visorbus/visorchipset.c

View file