diff options
| author | Arjan van de Ven <arjan@linux.intel.com> | 2008-09-21 06:09:00 +0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2008-10-16 20:24:50 +0400 |
| commit | 728f08934b087b96aacb00467f5551e0a5593fca (patch) | |
| tree | 94342640e5bca8b8c350fecbd05ff4e9bef0f8d0 /scripts/mkmakefile | |
| parent | e61396627f91abb855ddd8925be9172fb5871944 (diff) | |
| download | linux-728f08934b087b96aacb00467f5551e0a5593fca.tar.xz | |
debug: use dev_WARN() rather than WARN_ON() in device_pm_add()
device_pm_add() has a WARN_ON that is showing relatively high on
kerneloops.org, but unfortunately the WARN_ON is less than useful
in that it doesn't print any information about what device is causing
the issue.
This patch fixes this by turning the WARN_ON() into the newly
introduces dev_WARN() which will print information about the
device in question.
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'scripts/mkmakefile')
0 files changed, 0 insertions, 0 deletions