On 12/03/2013 07:51 AM, Jingoo Han wrote:
The driver core clears the driver data to NULL after device_release
or on probe failure. Thus, it is not needed to manually clear the
device driver data to NULL.
Signed-off-by: Jingoo Han
Acked-by: Simon Horman
---
Applied to my tree for 3.14
On 12/03/2013 07:51 AM, Jingoo Han wrote:
The driver core clears the driver data to NULL after device_release
or on probe failure. Thus, it is not needed to manually clear the
device driver data to NULL.
Signed-off-by: Jingoo Han jg1@samsung.com
Acked-by: Simon Horman
The driver core clears the driver data to NULL after device_release
or on probe failure. Thus, it is not needed to manually clear the
device driver data to NULL.
Signed-off-by: Jingoo Han
Acked-by: Simon Horman
---
drivers/clocksource/sh_mtu2.c |1 -
1 file changed, 1 deletion(-)
diff
The driver core clears the driver data to NULL after device_release
or on probe failure. Thus, it is not needed to manually clear the
device driver data to NULL.
Signed-off-by: Jingoo Han jg1@samsung.com
Acked-by: Simon Horman horms+rene...@verge.net.au
---
drivers/clocksource/sh_mtu2.c |
The driver core clears the driver data to NULL after device_release
or on probe failure. Thus, it is not needed to manually clear the
device driver data to NULL.
Signed-off-by: Jingoo Han
---
drivers/clocksource/sh_mtu2.c |1 -
1 file changed, 1 deletion(-)
diff --git
The driver core clears the driver data to NULL after device_release
or on probe failure. Thus, it is not needed to manually clear the
device driver data to NULL.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/clocksource/sh_mtu2.c |1 -
1 file changed, 1 deletion(-)
diff --git
6 matches
Mail list logo