diff options
| author | Brian Norris <briannorris@chromium.org> | 2017-12-19 02:30:48 +0300 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2017-12-19 04:45:06 +0300 |
| commit | 86ddd2db1f75a30f21a4c4de7a29249ee8c37ed8 (patch) | |
| tree | 032de1db029bf4dc765f8918607ef44e0a706d81 /drivers/base | |
| parent | c51a024e3913e9dbaf4dfcb9aaba825668a89ace (diff) | |
| download | linux-86ddd2db1f75a30f21a4c4de7a29249ee8c37ed8.tar.xz | |
PM / wakeup: only recommend "call"ing device_init_wakeup() once
I'll admit admit it: I've written bad driver code that tries to
configure a device's wake IRQ without having called device_init_wakeup()
first. But do you really have to ask ask me twice?
Signed-off-by: Brian Norris <briannorris@chromium.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/base')
| -rw-r--r-- | drivers/base/power/wakeup.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/base/power/wakeup.c b/drivers/base/power/wakeup.c index 38559f04db2c..cb72965b3281 100644 --- a/drivers/base/power/wakeup.c +++ b/drivers/base/power/wakeup.c @@ -298,7 +298,7 @@ int device_wakeup_attach_irq(struct device *dev, ws = dev->power.wakeup; if (!ws) { - dev_err(dev, "forgot to call call device_init_wakeup?\n"); + dev_err(dev, "forgot to call device_init_wakeup?\n"); return -EINVAL; } |