linux-kernel - Re: x86: move dma32_reserve_bootmem() after reserve

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 28 Jul 2008 17:25:12 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Bernhard Walle <bwalle@...e.de>
Cc:	linux-kernel@...r.kernel.org,
	the arch/x86 maintainers <x86@...nel.org>
Subject: Re: x86: move dma32_reserve_bootmem() after reserve_crashkernel()


* Bernhard Walle <bwalle@...e.de> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/