28 Apr
2015
28 Apr
'15
2:42 p.m.
Hi,
On 24 April 2015 at 22:33, Simon Glass sjg@chromium.org wrote:
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
drivers/core/uclass.c | 5 +++++ 1 file changed, 5 insertions(+)
Applied to u-boot-dm.
I'll pull this in soon since it does break a number of things.
Regards, Simon