From owner-freebsd-current Tue Nov 30 15:48:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A3BA015899; Tue, 30 Nov 1999 15:48:50 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA10921; Tue, 30 Nov 1999 16:48:44 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA06179; Tue, 30 Nov 1999 16:49:23 -0700 (MST) Message-Id: <199911302349.QAA06179@harmony.village.org> To: Mike Smith Subject: Re: PCCARD eject freeze (was Re: your mail) Cc: Christopher Masto , Nick Hibma , FreeBSD CURRENT Mailing List In-reply-to: Your message of "Tue, 30 Nov 1999 15:35:44 PST." <199911302335.PAA02844@mass.cdrom.com> References: <199911302335.PAA02844@mass.cdrom.com> Date: Tue, 30 Nov 1999 16:49:23 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911302335.PAA02844@mass.cdrom.com> Mike Smith writes: : You should definitely check the delete result, yes. : : Also, are you calling bus_generic_detach() after deleting the child? : I got the impression from Doug that this is required... In the child? device_delete_child() already calls device_detach(child). I can't call anything on the child device after delete_child becuase it is gone (and the memory is freed). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message