diff options
| author | Stephen Warren <swarren@nvidia.com> | 2011-01-11 12:48:53 -0700 |
|---|---|---|
| committer | Mark Brown <broonie@opensource.wolfsonmicro.com> | 2011-01-13 14:18:03 +0000 |
| commit | 422650e65a41a61b2f92396dfa4faa6a4df89913 (patch) | |
| tree | 955c75a7badff9dfee6fec4a3134e844ca27012d /block/blk.h | |
| parent | 1500b7b5ffaacb8199e0a61162f5d349fb19acbe (diff) | |
ASoC: tegra: s/IS_ERR_OR_NULL/IS_ERR/ for clk_get_sys
A recent discussion on linux-arm-kernel noted that the value returned by
clk_get_sys is an opaque token, and not strictly a pointer; it is
meaningful only to the clock API, clients should not dereference the value,
and the clock API must accept any non-IS_ERR value it returned.
Hence, only IS_ERR is appropriate to interpret the result, not
IS_ERR_OR_NULL.
I checked that clk_get_sys in both ASoC's for-next and Tegra's for-next
do behave as described; NULL is not returned in the case of error.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Diffstat (limited to 'block/blk.h')
0 files changed, 0 insertions, 0 deletions