Re: [PATCH v2 02/14] i2c: mv64xxx: simplify optional reset handling

2017-03-23 Thread Wolfram Sang
On Wed, Mar 15, 2017 at 12:31:34PM +0100, Philipp Zabel wrote: > As of commit bb475230b8e5 ("reset: make optional functions really > optional"), the reset framework API calls use NULL pointers to describe > optional, non-present reset controls. > > This allows to return errors from

Re: [PATCH v2 02/14] i2c: mv64xxx: simplify optional reset handling

2017-03-23 Thread Wolfram Sang
On Wed, Mar 15, 2017 at 12:31:34PM +0100, Philipp Zabel wrote: > As of commit bb475230b8e5 ("reset: make optional functions really > optional"), the reset framework API calls use NULL pointers to describe > optional, non-present reset controls. > > This allows to return errors from

[PATCH v2 02/14] i2c: mv64xxx: simplify optional reset handling

2017-03-15 Thread Philipp Zabel
As of commit bb475230b8e5 ("reset: make optional functions really optional"), the reset framework API calls use NULL pointers to describe optional, non-present reset controls. This allows to return errors from devm_reset_control_get_optional and to call reset_control_(de)assert unconditionally.

[PATCH v2 02/14] i2c: mv64xxx: simplify optional reset handling

2017-03-15 Thread Philipp Zabel
As of commit bb475230b8e5 ("reset: make optional functions really optional"), the reset framework API calls use NULL pointers to describe optional, non-present reset controls. This allows to return errors from devm_reset_control_get_optional and to call reset_control_(de)assert unconditionally.