summaryrefslogtreecommitdiffstats
path: root/sys/net/if.c
diff options
context:
space:
mode:
authorphk <phk@FreeBSD.org>2003-09-28 20:48:13 +0000
committerphk <phk@FreeBSD.org>2003-09-28 20:48:13 +0000
commit050117a32706566ff27f8d7610837a96932e0d3d (patch)
tree4c59531a9f82b488f7fca22115ecb97e22c4abb0 /sys/net/if.c
parent184a5c6d6515c512601948f88c75a8e3ce1bf3c4 (diff)
downloadFreeBSD-src-050117a32706566ff27f8d7610837a96932e0d3d.zip
FreeBSD-src-050117a32706566ff27f8d7610837a96932e0d3d.tar.gz
I don't know from where the notion that device driver should or
even could call VOP_REVOKE() on vnodes associated with its dev_t's has originated, but it stops right here. If there are things people belive destroy_dev() needs to learn how to do, please tell me about it, preferably with a reproducible test case. Include <sys/uio.h> in bluetooth code rather than rely on <sys/vnode.h> to do so. The fact that some of the USB code needs to include <sys/vnode.h> still disturbs me greatly, but I do not have time to chase that.
Diffstat (limited to 'sys/net/if.c')
-rw-r--r--sys/net/if.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/net/if.c b/sys/net/if.c
index bddf781..42e3c57 100644
--- a/sys/net/if.c
+++ b/sys/net/if.c
@@ -470,7 +470,7 @@ if_detach(ifp)
* Clean up all addresses.
*/
ifaddr_byindex(ifp->if_index) = NULL;
- revoke_and_destroy_dev(ifdev_byindex(ifp->if_index));
+ destroy_dev(ifdev_byindex(ifp->if_index));
ifdev_byindex(ifp->if_index) = NULL;
while (if_index > 0 && ifaddr_byindex(if_index) == NULL)
OpenPOWER on IntegriCloud