2008-07-26 22:26:12

by Bernhard Walle

[permalink] [raw]
Subject: x86: move dma32_reserve_bootmem() after reserve_crashkernel()

Hi Ingo,

can you send 91467bdf6e53058af13fd255375d6634ba0c70e0 (in
x86/crashdump) to Linus still for 2.6.27? I want that also in stable
for 2.6.26, and Greg KH stated that it must be first in Linus' tree.

(Although that commit cannot be applied to -stable directly because of
the huge code unification in 2.6.27 on the x86 side.)


Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development


2008-07-28 15:25:39

by Ingo Molnar

[permalink] [raw]
Subject: Re: x86: move dma32_reserve_bootmem() after reserve_crashkernel()


* Bernhard Walle <[email protected]> wrote:

> Hi Ingo,
>
> can you send 91467bdf6e53058af13fd255375d6634ba0c70e0 (in
> x86/crashdump) to Linus still for 2.6.27? I want that also in stable
> for 2.6.26, and Greg KH stated that it must be first in Linus' tree.

ok - i've merged it into x86/urgent.

Ingo

2008-07-28 16:00:29

by Bernhard Walle

[permalink] [raw]
Subject: Re: x86: move dma32_reserve_bootmem() after reserve_crashkernel()

* Ingo Molnar [2008-07-28 17:25]:
>
>
> * Bernhard Walle <[email protected]> wrote:
>
> > Hi Ingo,
> >
> > can you send 91467bdf6e53058af13fd255375d6634ba0c70e0 (in
> > x86/crashdump) to Linus still for 2.6.27? I want that also in stable
> > for 2.6.26, and Greg KH stated that it must be first in Linus' tree.
>
> ok - i've merged it into x86/urgent.

Thanks.



Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development