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.

diff --git a/sys/kern/bus_if.m b/sys/kern/bus_if.m
index cce997cff79f420f5f0130544d2775c68ffc4729..bafa448488cf9875ad989172becb272996a55471 100644 (file)
--- 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