The patch titled
Subject: drivers/rtc/rtc-pcf8563.c: fix irq request
has been added to the -mm tree. Its filename is
rtc-rtc-pcf8563-fix-irq-request.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/rtc-rtc-pcf8563-fix-irq-request.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/rtc-rtc-pcf8563-fix-irq-request.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Vincent Donnefort <vdonnefort@xxxxxxxxx>
Subject: drivers/rtc/rtc-pcf8563.c: fix irq request
pcf8563_probe() failed to check the devm_rtc_device_register() return value.
Signed-off-by: Vincent Donnefort <vdonnefort@xxxxxxxxx>
Reported-by: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/rtc/rtc-pcf8563.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff -puN drivers/rtc/rtc-pcf8563.c~rtc-rtc-pcf8563-fix-irq-request drivers/rtc/rtc-pcf8563.c
--- a/drivers/rtc/rtc-pcf8563.c~rtc-rtc-pcf8563-fix-irq-request
+++ a/drivers/rtc/rtc-pcf8563.c
@@ -419,7 +419,8 @@ static int pcf8563_probe(struct i2c_clie
pcf8563_driver.driver.name,
&pcf8563_rtc_ops, THIS_MODULE);
- return PTR_ERR_OR_ZERO(pcf8563->rtc);
+ if (IS_ERR(pcf8563->rtc))
+ return PTR_ERR(pcf8563->rtc);
if (client->irq > 0) {
err = devm_request_threaded_irq(&client->dev, client->irq,
_
Patches currently in -mm which might be from vdonnefort@xxxxxxxxx are
rtc-rtc-pcf8563-introducing-readwrite_block_data.patch
rtc-rtc-pcf8563-add-alarm-support.patch
rtc-rtc-pcf8563-fix-irq-request.patch
linux-next.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
