From 83a283cf62c7e1a69f5973aeff4ab00ef437b546 Mon Sep 17 00:00:00 2001 From: Warner Losh Date: Wed, 28 Oct 2015 18:53:18 +0000 Subject: [PATCH] Add a note to the effect that BUS_ADD_CHILD calls device_add_child_ordered to add the child. device_add_child_ordered doesn't call BUS_ADD_CHILD. --- sys/kern/bus_if.m | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/sys/kern/bus_if.m b/sys/kern/bus_if.m index cce997cff79..bafa448488c 100644 --- a/sys/kern/bus_if.m +++ b/sys/kern/bus_if.m @@ -209,7 +209,9 @@ METHOD void driver_added { * For busses which use use drivers supporting DEVICE_IDENTIFY() to * enumerate their devices, this method is used to create new * device instances. The new device will be added after the last - * existing child with the same order. + * existing child with the same order. Implementations of bus_add_child + * call device_add_child_ordered to add the child and often add + * a suitable ivar to the device specific to that bus. * * @param _dev the bus device which will be the parent of the * new child device