summaryrefslogtreecommitdiffstats
path: root/drivers/mfd
diff options
context:
space:
mode:
authorRussell King <rmk+kernel@arm.linux.org.uk>2012-02-07 11:03:23 +0000
committerRussell King <rmk+kernel@arm.linux.org.uk>2012-02-13 10:00:39 +0000
commit70d669de7356f6476db454dd8d053cd9c674a0d5 (patch)
treed71e3018964cb80fb8a00dabdb8aa74b6814e69c /drivers/mfd
parent4f8a428dac431e7bd09673b404769d87df948eef (diff)
downloadlinux-70d669de7356f6476db454dd8d053cd9c674a0d5.tar.gz
linux-70d669de7356f6476db454dd8d053cd9c674a0d5.tar.bz2
linux-70d669de7356f6476db454dd8d053cd9c674a0d5.zip
ARM: omap: resolve nebulous 'Error setting wl12xx data'
It's useful to print the error code when a called function fails so a diagnosis of why it failed is possible. In this case, it fails because we try to register some data for the wl12xx driver, but as the driver is not configured, a stub function is used which simply returns -ENOSYS. Let's do the simple thing for -rc and print the error code. Also, the return code from platform_register_device() at each of these sites was not being checked. Add some checking, and again print the error code. This should be fixed properly for the next merge window so we don't issue error messages merely because a driver is not configured. Acked-by: Tony Lindgren <tony@atomide.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'drivers/mfd')
0 files changed, 0 insertions, 0 deletions