diff options
| author | phk <phk@FreeBSD.org> | 2003-09-28 20:48:13 +0000 |
|---|---|---|
| committer | phk <phk@FreeBSD.org> | 2003-09-28 20:48:13 +0000 |
| commit | 050117a32706566ff27f8d7610837a96932e0d3d (patch) | |
| tree | 4c59531a9f82b488f7fca22115ecb97e22c4abb0 /sys/dev/nmdm/nmdm.c | |
| parent | 184a5c6d6515c512601948f88c75a8e3ce1bf3c4 (diff) | |
| download | FreeBSD-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/dev/nmdm/nmdm.c')
| -rw-r--r-- | sys/dev/nmdm/nmdm.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/sys/dev/nmdm/nmdm.c b/sys/dev/nmdm/nmdm.c index a899176..1511e9b 100644 --- a/sys/dev/nmdm/nmdm.c +++ b/sys/dev/nmdm/nmdm.c @@ -604,8 +604,8 @@ nmdmshutdown(void) nextdev2 = makedev(CDEV_MAJOR, (i+i) + 1); ptr1 = nextdev1->si_drv1; if (ptr1) { - revoke_and_destroy_dev(nextdev1); - revoke_and_destroy_dev(nextdev2); + destroy_dev(nextdev1); + destroy_dev(nextdev2); free(ptr1, M_NLMDM); } else { freedev(nextdev1); |
