[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071113195646.GD8421@austin.ibm.com>
Date: Tue, 13 Nov 2007 13:56:46 -0600
From: linas@...tin.ibm.com (Linas Vepstas)
To: Alex Chiang <achiang@...com>
Cc: gregkh@...e.de, kristen.c.accardi@...el.com, lenb@...nel.org,
matthew@....cx, richard.jones2@...com,
linux-kernel@...r.kernel.org, linux-pci@...ey.karlin.mff.cuni.cz,
pcihpd-discuss@...ts.sourceforge.net, linux-acpi@...r.kernel.org
Subject: Re: [PATCH 3/5, RFC] Introduce pci_slot
On Mon, Nov 12, 2007 at 05:14:47PM -0700, Alex Chiang wrote:
> +/* pci_slot represents a physical slot */
> +struct pci_slot {
> + struct pci_bus *bus; /* The bus this slot is on */
> + struct pci_slot *next; /* Next slot on this bus */
> + struct hotplug_slot *hotplug; /* Hotplug info (migrate over time) */
How much migration do you expect? Some of it? All of it? If the
answer is "all of it", wouldn't it just be easier to rename
struct hotplug_slot, and go from there?
--linas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists