summaryrefslogtreecommitdiff
path: root/test/dm/virtio_rng.c
diff options
context:
space:
mode:
authorMichal Suchanek <msuchanek@suse.de>2022-10-12 21:57:59 +0200
committerSimon Glass <sjg@chromium.org>2022-10-17 21:17:12 -0600
commitc726fc01cf669e3e2979da8665ef660e7d3ba464 (patch)
tree5d11dc2d0e58fac8a08cb1e2425ff0ae10ad0a8a /test/dm/virtio_rng.c
parent8676ae36ae4617b20b5cc49972c54c63c7b27bb3 (diff)
dm: treewide: Use uclass_first_device_err when accessing one device
There is a number of users that use uclass_first_device to access the first and (assumed) only device in uclass. Some check the return value of uclass_first_device and also that a device was returned which is exactly what uclass_first_device_err does. Some are not checking that a device was returned and can potentially crash if no device exists in the uclass. Finally there is one that returns NULL on error either way. Convert all of these to use uclass_first_device_err instead, the return value will be removed from uclass_first_device in a later patch. Signed-off-by: Michal Suchanek <msuchanek@suse.de> Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'test/dm/virtio_rng.c')
-rw-r--r--test/dm/virtio_rng.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/test/dm/virtio_rng.c b/test/dm/virtio_rng.c
index ff5646b4e11..8b9a04b1fde 100644
--- a/test/dm/virtio_rng.c
+++ b/test/dm/virtio_rng.c
@@ -28,7 +28,7 @@ static int dm_test_virtio_rng_check_len(struct unit_test_state *uts)
u8 buffer[16];
/* check probe success */
- ut_assertok(uclass_first_device(UCLASS_VIRTIO, &bus));
+ ut_assertok(uclass_first_device_err(UCLASS_VIRTIO, &bus));
ut_assertnonnull(bus);
/* check the child virtio-rng device is bound */