diff options
| author | Poul-Henning Kamp <phk@FreeBSD.org> | 2003-09-28 20:48:13 +0000 |
|---|---|---|
| committer | Poul-Henning Kamp <phk@FreeBSD.org> | 2003-09-28 20:48:13 +0000 |
| commit | ed692400eba222d9abc1884e9bb7746c9bc71437 (patch) | |
| tree | 4c59531a9f82b488f7fca22115ecb97e22c4abb0 /sys/dev/usb/uscanner.c | |
| parent | 6dcf0a53d24001457fcad982452de21a062426b6 (diff) | |
| download | src-ed692400eba222d9abc1884e9bb7746c9bc71437.tar.gz src-ed692400eba222d9abc1884e9bb7746c9bc71437.zip | |
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.
Notes
Notes:
svn path=/head/; revision=120559
Diffstat (limited to 'sys/dev/usb/uscanner.c')
| -rw-r--r-- | sys/dev/usb/uscanner.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/sys/dev/usb/uscanner.c b/sys/dev/usb/uscanner.c index 8615d9a8fd36..5d82960f427c 100644 --- a/sys/dev/usb/uscanner.c +++ b/sys/dev/usb/uscanner.c @@ -620,7 +620,6 @@ USB_DETACH(uscanner) int maj, mn; #elif defined(__FreeBSD__) dev_t dev; - struct vnode *vp; #endif #if defined(__NetBSD__) || defined(__OpenBSD__) @@ -657,9 +656,6 @@ USB_DETACH(uscanner) #elif defined(__FreeBSD__) /* destroy the device for the control endpoint */ dev = makedev(USCANNER_CDEV_MAJOR, USBDEVUNIT(sc->sc_dev)); - vp = SLIST_FIRST(&dev->si_hlist); - if (vp) - VOP_REVOKE(vp, REVOKEALL); destroy_dev(dev); #endif |