There is no need to remember which usb(4) device is the child of an USB
authormpi <mpi@openbsd.org>
Mon, 19 May 2014 13:11:31 +0000 (13:11 +0000)
committermpi <mpi@openbsd.org>
Mon, 19 May 2014 13:11:31 +0000 (13:11 +0000)
commitad21ef7776a2ecbad05f6bd6abbe5e259f5510fd
tree9b87f9c12a74a79cf17fc489ff98e577e5d7a850
parent0c1016a616438dd32e279287701e67bdf48fcac5
There is no need to remember which usb(4) device is the child of an USB
host controller because autoconf(9) already does it.

Breakage reported by todd@
sys/arch/arm/xscale/pxa2x0_ohci.c
sys/arch/armv7/imx/imxehci.c
sys/arch/armv7/omap/omehci.c
sys/arch/armv7/omap/omohci.c
sys/arch/armv7/sunxi/sxiehci.c
sys/arch/loongson/dev/ohci_voyager.c
sys/arch/socppc/dev/ehci_obio.c