On Fri, Jun 22, 2012 at 4:41 AM, Jiang Liu <liuj97@xxxxxxxxx> wrote: > On 06/22/2012 06:21 PM, Taku Izumi wrote: >> On Thu, 21 Jun 2012 11:18:07 -0700 >> Yinghai Lu <yinghai@xxxxxxxxxx> wrote: >> >>> On Thu, Jun 21, 2012 at 2:34 AM, Taku Izumi <izumi.taku@xxxxxxxxxxxxxx> wrote: >>>> >>>> This patchset adds basic code for host bridge hotplug. >>>> >>>> I assume ACPI container device (ACPI0004) which carries >>>> hostbridges will be hot-added or hot-removed. In that case >>>> some codes are now missing for hostbridge hotplug. >>>> This patchset mainly adds the following: >>>> - remove hostbridge and devices under it >>>> - resoruce-assign code for devices under hot-added hostbridge >>>> >>>> The behavior when you don't try hostbridge hotplug should not change. >>>> >>>> *[PATCH 1/4] acpi, pci: introduce list for acpi_pci_root drivers >>>> *[PATCH 2/4] acpi, pci: introduce acpi_root_sem for list manipulation >>>> *[PATCH 3/4] acpi, pci: add hostbridge removal function >>>> *[PATCH 4/4] acpi, pci: add resoruce-assign code for devices under >>>> hot-added hostbridge >>> >>> Hi, did you check our pci root bus hot plug branch ? >>> >>> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git >>> for-pci-root-bus-hotplug >>> >>> It contain some similar patches from jiang and me. >> >> Hi Yinghai, >> Thank you for your comment. >> >> I checked your branch out. It seems to include many work. >> Is it already scheduled to be merged to Bjorn's tree? >> If not, should I develop based on your tree? > Hi Taku, > I think the target is to merge those changes into Bjorn gate in near future, > so it would be better to base on Yinghai's gate. As you can probably tell, I'm falling behind in getting things merged. If you can agree among yourselves on which series is preferable *and* spend some time reviewing each other's patches and adding "Reviewed-by", that would help me out be resolving some of the issues. Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
