[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAE9FiQX57=cmfgJJv5E_rTQD1umCsmqJas0Sa22sN_xhdCSUgw@mail.gmail.com>
Date: Thu, 1 Mar 2012 11:03:15 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: Myron Stowe <myron.stowe@...il.com>
Cc: Jesse Barnes <jbarnes@...tuousgeek.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Tony Luck <tony.luck@...el.com>,
David Miller <davem@...emloft.net>, x86 <x86@...nel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Dominik Brodowski <linux@...inikbrodowski.net>,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arch@...r.kernel.org
Subject: Re: [PATCH 00/39] PCI: pci_host_bridge related cleanup and busn_alloc
On Thu, Mar 1, 2012 at 10:51 AM, Myron Stowe <myron.stowe@...il.com> wrote:
> On Wed, Feb 29, 2012 at 4:06 PM, Yinghai Lu <yinghai@...nel.org> wrote:
>> The first 14 patches are hostbridge clean up.
>> will add struct device dev into host_bridge struct.
>> also will add release support to make sure allocated resource get
>> freed during root bus removal including hostbridge and pci_sysdata.
>>
>> others 25 patches are busn_alloc related.
>> Set up iobusn_resource tree, and register bus number range to it.
>> Later when need to find bus range, will try to allocate from the tree
>> Need to test on arches other than x86. esp for ia64 and powerpc that support
>> more than on peer root buses.
>
> Why did you collapse these two series into one at this point?
>
> Last I was keeping up with - there was a -v9 00/23 series related to
> bus_num and a -v2 00/11 series for pci_host_bridge related cleanup.
the updated busn_alloc patchset, need to be applied on top of
pci_host_bridge related cleanup.
So i was thinking put them together would be better to be reviewed
first 14 for hostbridge clean up. and others for busn_res_alloc.
>
> As a distro maintainer I need to try and keep up with what is occurring
> here and actions like this - coalescing multiple series - unnecessarily
> complicates things. It also masks the fact that the bus_num series is
> now on -v10 within a very short time frame (which implies a lot).
I will separate them in next revision, if Jesse would not pick up
first 14 shortly.
Thanks
Yinghai
--
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