On Tue, Jan 15, 2008 at 11:00:37AM -0500, Loic Prylli wrote: > > > On 1/14/2008 6:04 PM, Adrian Bunk wrote: >>> I thought so, but due to the way that things are initialised, mmconfig >>> happens before conf1. conf1 is known to be usable, but hasn't set >>> raw_pci_ops at this point. Confusing, and not ideal, but fixing this >>> isn't in scope for 2.6.24. >>> ... >>> >> >> *ahem* >> >> I don't think anything of what was discussed in this thread would be in >> scope for 2.6.24 (unless Linus wants to let the bunny that brings eggs >> release 2.6.24). >> >> cu >> Adrian >> > > > Why not put in 2.6.24 a simple fix for the last known remaining mmconfig > problems in 2.6.24?
Heh, no, because it is _way_ too late for such a patch that hasn't been tested in any trees, sorry. 2.6.25 is the earliest I'll take such a fix, and if it's really as simple as you say, I'll consider it for the -stable releases for .24 if needed. But so far, we have a zillion patches floating around, claiming different things, some with signed-off-bys and others without, so for now, I'll just stick with Arjan's patch in -mm and see if anyone complains about those releases... thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/