[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20171218233048.156954-1-briannorris@chromium.org>
Date: Mon, 18 Dec 2017 15:30:48 -0800
From: Brian Norris <briannorris@...omium.org>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>
Cc: <linux-kernel@...r.kernel.org>, linux-pm@...r.kernel.org,
Tony Lindgren <tony@...mide.com>,
Brian Norris <briannorris@...omium.org>
Subject: [PATCH TRIVIAL] 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@...omium.org>
---
drivers/base/power/wakeup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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;
}
--
2.15.1.504.g5279b80103-goog
Powered by blists - more mailing lists