From 050117a32706566ff27f8d7610837a96932e0d3d Mon Sep 17 00:00:00 2001 From: phk Date: Sun, 28 Sep 2003 20:48:13 +0000 Subject: 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 in bluetooth code rather than rely on to do so. The fact that some of the USB code needs to include still disturbs me greatly, but I do not have time to chase that. --- sys/dev/nmdm/nmdm.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'sys/dev/nmdm/nmdm.c') 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); -- cgit v1.1