Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760718AbYCZRIr (ORCPT ); Wed, 26 Mar 2008 13:08:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756809AbYCZRI1 (ORCPT ); Wed, 26 Mar 2008 13:08:27 -0400 Received: from g5t0008.atlanta.hp.com ([15.192.0.45]:29079 "EHLO g5t0008.atlanta.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753342AbYCZRI0 (ORCPT ); Wed, 26 Mar 2008 13:08:26 -0400 Message-Id: <20080326171058.099442579@ldl.fc.hp.com> User-Agent: quilt/0.46-1 Date: Wed, 26 Mar 2008 11:10:58 -0600 From: Bjorn Helgaas To: Len Brown Cc: linux-acpi@vger.kernel.org Cc: linux-kernel@vger.kernel.org Cc: Adam Belay Cc: Li Shaohua Cc: Matthieu Castet Cc: Thomas Renninger Cc: Rene Herman Cc: Jaroslav Kysela Cc: Andrew Morton Subject: [patch 00/37] PNP resource_table cleanups Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1148 Lines: 28 This series of patches does some PNP housecleaning and consolidation. PNP currently uses a fixed-size table (pnp_resource_table) to track the IO, MMIO, IRQ, and DMA resources used by a device. Some motherboard devices have many resources, so we've been plagued by table overflows and we've had to drastically increase the table size, which wastes a lot of memory. The end goal is to replace that fixed-size table with something more dynamic. These patches don't go that far, but they do make pnp_resource_table private to the PNP core and centralize all references to it in a small set of shared functions. In addition, this series contains a number of related cleanups, like centralized allocation of struct pnp_dev, conversion to dev_printk when possible, removing many PNP core internal functions from the public interface, and alignment of the ISAPNP, PNPBIOS, and PNPACPI backends. Bjorn -- -- 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/