mtd/maps/physmap: catch failure to register MTD_PHYSMAP_COMPAT device
authorH Hartley Sweeten <hartleys@visionengravers.com>
Fri, 2 Apr 2010 22:46:30 +0000 (17:46 -0500)
committerDavid Woodhouse <David.Woodhouse@intel.com>
Tue, 20 Apr 2010 07:53:52 +0000 (08:53 +0100)
commit1ca5d2f0196cfca678086fa6f88eec4f9d0307ee
tree2d867897b6c6c88e912b60ca98ff06aaf98f1642
parentfed457a83611182f5a2e049cce02f8f4e1b65644
mtd/maps/physmap: catch failure to register MTD_PHYSMAP_COMPAT device

If the default Kconfig values are used with MTD_PHYSMAP_COMPAT you end
up with a resource where end < start.  This causes __request_resource to
return a conflict which then returns an -EBUSY error code.  The current
physmap.c code just assumes that the platfom_device_register will always
succeed.

Catch this failure during the physmap_init and propogate the error.

Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
Reported-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
drivers/mtd/maps/physmap.c