Re: [PATCH v2] reset: fix optional reset_control_get stubs to return NULL

2017-03-20 Thread Andrzej Hajda
On 20.03.2017 12:17, Philipp Zabel wrote: > When RESET_CONTROLLER is not enabled, the optional reset_control_get > stubs should now also return NULL. > > Since it is now valid for reset_control_assert/deassert/reset/status/put > to be called unconditionally, with NULL as an argument for optional >

Re: [PATCH v2] reset: fix optional reset_control_get stubs to return NULL

2017-03-20 Thread Andrzej Hajda
On 20.03.2017 12:17, Philipp Zabel wrote: > When RESET_CONTROLLER is not enabled, the optional reset_control_get > stubs should now also return NULL. > > Since it is now valid for reset_control_assert/deassert/reset/status/put > to be called unconditionally, with NULL as an argument for optional >

[PATCH v2] reset: fix optional reset_control_get stubs to return NULL

2017-03-20 Thread Philipp Zabel
When RESET_CONTROLLER is not enabled, the optional reset_control_get stubs should now also return NULL. Since it is now valid for reset_control_assert/deassert/reset/status/put to be called unconditionally, with NULL as an argument for optional resets, the stubs are not allowed to warn anymore.

[PATCH v2] reset: fix optional reset_control_get stubs to return NULL

2017-03-20 Thread Philipp Zabel
When RESET_CONTROLLER is not enabled, the optional reset_control_get stubs should now also return NULL. Since it is now valid for reset_control_assert/deassert/reset/status/put to be called unconditionally, with NULL as an argument for optional resets, the stubs are not allowed to warn anymore.