diff options
| author | Simon Glass <sjg@chromium.org> | 2015-04-24 22:33:07 -0600 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2015-04-28 16:49:03 -0600 |
| commit | f66529f998e59acbd64ccce3adfce8eedfa52da8 (patch) | |
| tree | 417083ee2a5060354f7c7b729c75cc9c655e4ca3 /arch | |
| parent | 4f60166c909f40da6aee14b810806dfa9f553bbc (diff) | |
dm: core: Correct bug introduced in uclass_first/next_device()
These functions now rely on uclass_find_first/next_device() and assume that
they will either return failure (-ve error code) or a device. In fact,
coming to the end of a list is not considered failure and they return 0
in that case.
The logic to deal with this was replaced in commit acb9ca2a with just using
uclass_get_device_tail(). Add back the missing logic. This bug was
caught by unit tests but since they were broken for other reasons at the
time, this was not noticed.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions