summaryrefslogtreecommitdiffstats
path: root/common
diff options
context:
space:
mode:
authorAlexander Aring <alex.aring@gmail.com>2014-06-23 10:00:00 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2014-06-24 08:07:45 +0200
commitc9e2e08edcdce4205821226817686e62dc349eab (patch)
treef92d38dbc7fe5545d23dda2243b0d188c9bd16d6 /common
parentb3a667cd841802074f5d97453c4ba6364c706c27 (diff)
downloadbarebox-c9e2e08edcdce4205821226817686e62dc349eab.tar.gz
common: resource: print conflicts as warning
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 many other outputs. This patch replace the debug print to a warning printout. A conflict should normally never happen. If there is a conflict it's much easier to see it with this patch. Signed-off-by: Alexander Aring <alex.aring@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'common')
-rw-r--r--common/resource.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/common/resource.c b/common/resource.c
index fe4680e..1ea2a75 100644
--- a/common/resource.c
+++ b/common/resource.c
@@ -71,7 +71,7 @@ struct resource *__request_region(struct resource *parent,
goto ok;
if (start > r->end)
continue;
- debug("%s: 0x%08llx:0x%08llx conflicts with 0x%08llx:0x%08llx\n",
+ pr_warn("%s: 0x%08llx:0x%08llx conflicts with 0x%08llx:0x%08llx\n",
__func__,
(unsigned long long)start,
(unsigned long long)end,