On Thu, Jun 23, 2011 at 1:37 PM, Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx> wrote:
>
> Just a few minor fixes. We have one open issue with the resource
> re-allocation code that was re-added. Ram has a fix but I'm concerned
> it will introduce other regressions. So at this point we have a few
> options:
> - revert the bridge resource re-allocation code (again)
> - hide the re-allocation code behind a new kernel option (and not
> try=!), this would at least let us experiment with new strategies
> and PNP resource tracking etc
> - apply Ram's patch and revert it all later if things are still broken
I think I've missed the regression discussion, so can you forward a
description and the fix?
I have to admit that I'm inclined to try the fix if it's clean, just
in the hope to get over this finally. But I'd like to see what the
problem/fix is...
Maybe I've seen it and just didn't react.
Linus
--
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
