Hi Kevin,
On Tue, 17 Nov 2009, Kevin Hilman wrote:
The _dev_wakeup_lat_limit field of struct omap_device is u32, so use
UINT_MAX instead of INT_MAX for the default maximum.
Signed-off-by: Kevin Hilman khil...@deeprootsystems.com
Indeed, thanks. Will add this to the second version of the fixes series.
- Paul
---
arch/arm/plat-omap/omap_device.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/plat-omap/omap_device.c
b/arch/arm/plat-omap/omap_device.c
index 83bee1c..9ec3735 100644
--- a/arch/arm/plat-omap/omap_device.c
+++ b/arch/arm/plat-omap/omap_device.c
@@ -468,7 +468,7 @@ int omap_device_enable(struct platform_device *pdev)
ret = _omap_device_activate(od, IGNORE_WAKEUP_LAT);
od-dev_wakeup_lat = 0;
- od-_dev_wakeup_lat_limit = INT_MAX;
+ od-_dev_wakeup_lat_limit = UINT_MAX;
od-_state = OMAP_DEVICE_STATE_ENABLED;
return ret;
--
1.6.5.1
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
