On 03/06/2015 09:18 PM, Mike Turquette wrote:
Quoting Tero Kristo (2015-02-25 11:04:18)
There is a case where NULL can be a valid return value for
ti_clk_get_reg_addr, specifically the case where both the provider index
and register offsets are zero. In this case, the current error checking
On 03/18/2015 07:02 PM, Tony Lindgren wrote:
* Tero Kristo t-kri...@ti.com [150318 00:06]:
On 03/17/2015 08:38 PM, Tony Lindgren wrote:
* Mike Turquette mturque...@linaro.org [150306 11:18]:
Quoting Tero Kristo (2015-02-25 11:04:18)
There is a case where NULL can be a valid return value for
* Tero Kristo t-kri...@ti.com [150318 00:06]:
On 03/17/2015 08:38 PM, Tony Lindgren wrote:
* Mike Turquette mturque...@linaro.org [150306 11:18]:
Quoting Tero Kristo (2015-02-25 11:04:18)
There is a case where NULL can be a valid return value for
ti_clk_get_reg_addr, specifically the case
On 03/17/2015 08:38 PM, Tony Lindgren wrote:
* Mike Turquette mturque...@linaro.org [150306 11:18]:
Quoting Tero Kristo (2015-02-25 11:04:18)
There is a case where NULL can be a valid return value for
ti_clk_get_reg_addr, specifically the case where both the provider index
and register offsets
* Mike Turquette mturque...@linaro.org [150306 11:18]:
Quoting Tero Kristo (2015-02-25 11:04:18)
There is a case where NULL can be a valid return value for
ti_clk_get_reg_addr, specifically the case where both the provider index
and register offsets are zero. In this case, the current error
Quoting Tero Kristo (2015-02-25 11:04:18)
There is a case where NULL can be a valid return value for
ti_clk_get_reg_addr, specifically the case where both the provider index
and register offsets are zero. In this case, the current error checking
against a NULL pointer will fail. Thus, change
