Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 14 Aug 2002 22:21:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 14 Aug 2002 22:21:05 -0400 Received: from hdfdns01.hd.intel.com ([192.52.58.10]:56299 "EHLO mail1.hd.intel.com") by vger.kernel.org with ESMTP id ; Wed, 14 Aug 2002 22:21:04 -0400 Message-ID: From: "Grover, Andrew" To: "'colpatch@us.ibm.com'" , Linus Torvalds Cc: Alan Cox , "Martin J. Bligh" , linux-kernel@vger.kernel.org, Michael Hohnbaum , Greg KH , jgarzik@mandrakesoft.com, "Grover, Andrew" , "Diefenbaugh, Paul S" Subject: RE: [patch] PCI Cleanup Date: Wed, 14 Aug 2002 19:24:49 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1230 Lines: 30 > From: Matthew Dobson [mailto:colpatch@us.ibm.com] > OK... Here's the latest version. Sorry about that last > posting... Stupid line > wrapping broke the patch! :( This patch also removes the > pci_config_(read|write) function pointers. People shouldn't > be using these (I > don't think) and should be using the pci_ops structure linked > through the > pci_dev structure. These end up calling the same functions that the > pci_config_(read|write) pointers refer to anyway. The only > places I can see > that these are being used in the kernel are in > drivers/acpi/osl.c... Anyone > care to comment on the use there or if it can be changed? > I've cc'd the > authors of the file... Hi Matthew, ACPI needs access to PCI config space, and it doesn't have a struct pci_dev to pass to access functions. It doesn't look like your patch exposes an interface that 1) doesn't require a pci_dev and 2) abstracts the PCI config access method, does it? Regards -- Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/