Re: [PATCH] common: resource: print conflicts as warning

2014-06-24 Thread Sascha Hauer
On Mon, Jun 23, 2014 at 10:00:00AM +0200, Alexander Aring wrote: Crazy things happen if there are resource conflicts and a device probe runs dev_request_mem_region. The dev_request_mem_region returns a start pointer which is zero. The probe function doesn't check on this and probing the device

[PATCH] common: resource: print conflicts as warning

2014-06-23 Thread Alexander Aring
Crazy things happen if there are resource conflicts and a device probe runs dev_request_mem_region. The dev_request_mem_region returns a start pointer which is zero. The probe function doesn't check on this and probing the device on zero base address. To debug this in debug log level there are