From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932101AbWFZOx4 (ORCPT ); Mon, 26 Jun 2006 10:53:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932318AbWFZOx4 (ORCPT ); Mon, 26 Jun 2006 10:53:56 -0400 Received: from wildsau.enemy.org ([193.170.194.34]:18590 "EHLO wildsau.enemy.org") by vger.kernel.org with ESMTP id S932101AbWFZOxz (ORCPT ); Mon, 26 Jun 2006 10:53:55 -0400 From: Herbert Rosmanith Message-Id: <200606261447.k5QElseJ013480@wildsau.enemy.org> Subject: Re: finding pci_dev from scsi_device In-Reply-To: <1151332900.3185.49.camel@laptopd505.fenrus.org> To: Arjan van de Ven Date: Mon, 26 Jun 2006 16:47:54 +0200 (MET DST) CC: linux-kernel@vger.kernel.org X-Mailer: ELM [version 2.4ME+ PL100 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > > also.. you could just put your code into the remove hook... :) oh by the way, that's the reason why I need to find the pci-pointer myself. in our environment, the remove hook is never called. kind regards, h.rosmanith