linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <20080727002559.48cee0d4@kopernikus.site>
Date:	Sun, 27 Jul 2008 00:25:59 +0200
From:	Bernhard Walle <bwalle@...e.de>
To:	mingo@...e.hu, linux-kernel@...r.kernel.org
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
--
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/