Re: [PATCH 0/9] make clk_get_rate implementations behavior more consistent

Hi Jonas, On Tue, Jul 18, 2017 at 12:17 PM, Jonas Gorski wrote: > The common clock and several other clock API implementations allow > calling clk_get_rate with a NULL pointer. While not specified as > expected behavior of the API, device drivers have come to rely on

Re: [PATCH 0/9] make clk_get_rate implementations behavior more consistent

Hi Jonas, On Tue, Jul 18, 2017 at 12:17 PM, Jonas Gorski wrote: > The common clock and several other clock API implementations allow > calling clk_get_rate with a NULL pointer. While not specified as > expected behavior of the API, device drivers have come to rely on that, > causing them to OOPS

[PATCH 0/9] make clk_get_rate implementations behavior more consistent

The common clock and several other clock API implementations allow calling clk_get_rate with a NULL pointer. While not specified as expected behavior of the API, device drivers have come to rely on that, causing them to OOPS when run on a platform with a different clock API implementation. Fix

[PATCH 0/9] make clk_get_rate implementations behavior more consistent

The common clock and several other clock API implementations allow calling clk_get_rate with a NULL pointer. While not specified as expected behavior of the API, device drivers have come to rely on that, causing them to OOPS when run on a platform with a different clock API implementation. Fix