Subject: [obsolete] drivers-rtc-rtc-tps6586xc-device-wakeup-flags-correction.patch removed from -mm tree
To: digetx@xxxxxxxxx,ldewangan@xxxxxxxxxx,vbyravarasu@xxxxxxxxxx,mm-commits@xxxxxxxxxxxxxxx
From: akpm@xxxxxxxxxxxxxxxxxxxx
Date: Wed, 29 May 2013 13:04:59 -0700
The patch titled
Subject: drivers/rtc/rtc-tps6586x.c: device wakeup flags correction
has been removed from the -mm tree. Its filename was
drivers-rtc-rtc-tps6586xc-device-wakeup-flags-correction.patch
This patch was dropped because it is obsolete
------------------------------------------------------
From: Dmitry Osipenko <digetx@xxxxxxxxx>
Subject: drivers/rtc/rtc-tps6586x.c: device wakeup flags correction
Use device_init_wakeup() instead of device_set_wakeup_capable() and move
it before rtc dev registering. This fixes issue with alarmtimer that
checks wakeup capability with device_may_wakeup() on device add.
Signed-off-by: Dmitry Osipenko <digetx@xxxxxxxxx>
Cc: Laxman dewangan <ldewangan@xxxxxxxxxx>
Cc: Venu Byravarasu <vbyravarasu@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/rtc/rtc-tps6586x.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff -puN drivers/rtc/rtc-tps6586x.c~drivers-rtc-rtc-tps6586xc-device-wakeup-flags-correction drivers/rtc/rtc-tps6586x.c
--- a/drivers/rtc/rtc-tps6586x.c~drivers-rtc-rtc-tps6586xc-device-wakeup-flags-correction
+++ a/drivers/rtc/rtc-tps6586x.c
@@ -273,6 +273,8 @@ static int tps6586x_rtc_probe(struct pla
return ret;
}
+ device_init_wakeup(&pdev->dev, 1);
+
platform_set_drvdata(pdev, rtc);
rtc->rtc = devm_rtc_device_register(&pdev->dev, dev_name(&pdev->dev),
&tps6586x_rtc_ops, THIS_MODULE);
@@ -292,7 +294,6 @@ static int tps6586x_rtc_probe(struct pla
goto fail_rtc_register;
}
disable_irq(rtc->irq);
- device_set_wakeup_capable(&pdev->dev, 1);
return 0;
fail_rtc_register:
_
Patches currently in -mm which might be from digetx@xxxxxxxxx are
linux-next.patch
rtc-tps6586x-device-wakeup-flags-correction.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
