* Yinghai Lu <yhlu.kernel@gmail.com> wrote:

quoted text
> On Thu, Sep 4, 2008 at 12:04 PM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> >> v7: remove wrong removing of write_unlock(&resource_lock) in adjust_resource()
> >
> > i've applied the generic commit below to tip/core/resources, and merged
> > tip/core/resources into tip/x86/core, and added the remaining e820.c
> > oneliner change (attached below as well).
> >
> 
> wonder if need to put
> 
>   x86: split e820 reserved entries record to late v4
>   IO resources: add reserve_region_with_split()
>   x86: split e820 reserved entries record to late, v7
> 
> into 2.6.27 for fix hang on David's system.

too late i think. It hung on v2.6.26 too, right? So v2.6.28 would be 
more appropriate, and linux-next or tip/msater can be used as a 
practical kernel in the meanwhile.

	Ingo
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/