On Wed, 28 May 2008 17:04:34 -0600 Alex Chiang <achiang@xxxxxx> wrote: > > > > I assume these patches will destroy Alex's frequently-destroyed > > pci-hotplug-introduce-pci_slot.patch. Ho hum. > > I took a quick scan, and yeah, they'll break my patch series, but > I should be able to adapt. Ho hum indeed. > > More importantly though, I can't seem to get any help on the > pseries front. Benjamin Herrenschmidt is too busy, and I haven't > heard a single peep from the IBM fellow (Mike Mason). Ben, Paul: can you please help out here? The relevant patches are: http://userweb.kernel.org/~akpm/mmotm/broken-out/pci-hotplug-construct-one-fakephp-slot-per-pci-slot.patch http://userweb.kernel.org/~akpm/mmotm/broken-out/pci-hotplug-export-kobject_rename-for-pci_hotplug_core.patch http://userweb.kernel.org/~akpm/mmotm/broken-out/pci-hotplug-introduce-pci_slot.patch http://userweb.kernel.org/~akpm/mmotm/broken-out/pci-hotplug-acpi-pci-slot-detection-driver.patch > Any suggestions on how to move forward? My fixup patch did fix > Badari's original oops in a syntactically sane manner; it was the > semantics that were a bit trickier. What is "my fixup patch"? > Perhaps we could roll that last fixup patch into the series, aim > for the next merge window, and see who complains? Obviously I'd > work any issues that would pop up, and we could always revert it > as a last resort. > > Or is that idea too sloppy for mainline? Well we _could_ slam it all in and say "good luck". t'would be nice to get these things sorted out beforehand but this stuff has been floating about for two months now. (Hey, this is Jesse's problem, not mine ;)) -- 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
