Re: [U-Boot] [PATCH v2 3/3] dm: core: Add uclass_first/next_device_check()

2017-06-15 Thread sjg
On 06/09/2017 12:41 AM, Simon Glass wrote: > Hi, > > On 23 April 2017 at 20:10, Simon Glass wrote: >> Sometimes it is useful to iterate through all devices in a uclass and >> skip over those which do not work correctly (e.g fail to probe). Add two >> new functions to provide

Re: [U-Boot] [PATCH v2 3/3] dm: core: Add uclass_first/next_device_check()

2017-06-09 Thread Heinrich Schuchardt
On 06/09/2017 12:41 AM, Simon Glass wrote: > Hi, > > On 23 April 2017 at 20:10, Simon Glass wrote: >> Sometimes it is useful to iterate through all devices in a uclass and >> skip over those which do not work correctly (e.g fail to probe). Add two >> new functions to provide

Re: [U-Boot] [PATCH v2 3/3] dm: core: Add uclass_first/next_device_check()

2017-06-08 Thread Mario Six
Hi Simon, On Fri, Jun 9, 2017 at 12:41 AM, Simon Glass wrote: > Hi, > > On 23 April 2017 at 20:10, Simon Glass wrote: >> Sometimes it is useful to iterate through all devices in a uclass and >> skip over those which do not work correctly (e.g fail to

Re: [U-Boot] [PATCH v2 3/3] dm: core: Add uclass_first/next_device_check()

2017-06-08 Thread Simon Glass
Hi, On 23 April 2017 at 20:10, Simon Glass wrote: > Sometimes it is useful to iterate through all devices in a uclass and > skip over those which do not work correctly (e.g fail to probe). Add two > new functions to provide this feature. > > The caller must check the return

[U-Boot] [PATCH v2 3/3] dm: core: Add uclass_first/next_device_check()

2017-04-23 Thread Simon Glass
Sometimes it is useful to iterate through all devices in a uclass and skip over those which do not work correctly (e.g fail to probe). Add two new functions to provide this feature. The caller must check the return value each time to make sure that the device is valid. But the device pointer is