summaryrefslogtreecommitdiffstats
path: root/sys/kern
diff options
context:
space:
mode:
authorimp <imp@FreeBSD.org>2015-10-28 18:53:18 +0000
committerimp <imp@FreeBSD.org>2015-10-28 18:53:18 +0000
commit20050b3d3c4e35ce08bfa15784bd0948741eae6f (patch)
tree372f3b709440e018db2187685d696c7a2d60caab /sys/kern
parentf27a84317646769b581a8ee903a983af9306e6ec (diff)
downloadFreeBSD-src-20050b3d3c4e35ce08bfa15784bd0948741eae6f.zip
FreeBSD-src-20050b3d3c4e35ce08bfa15784bd0948741eae6f.tar.gz
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.
Diffstat (limited to 'sys/kern')
-rw-r--r--sys/kern/bus_if.m4
1 files changed, 3 insertions, 1 deletions
diff --git a/sys/kern/bus_if.m b/sys/kern/bus_if.m
index cce997c..bafa448 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
OpenPOWER on IntegriCloud