aboutsummaryrefslogtreecommitdiffstats
path: root/block
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2011-06-02 06:11:24 +0900
committerLinus Torvalds <torvalds@linux-foundation.org>2011-06-02 06:11:24 +0900
commit1fa7b6a29c61358cc2ca6f64cef4aa0e1a7ca74c (patch)
tree7318c8602f61c2052df308920bd681539f760555 /block
parentf0f52a9463839c52a63c05d6e7d4a330d94a9794 (diff)
downloadautogen-1fa7b6a29c61358cc2ca6f64cef4aa0e1a7ca74c.tar.gz
autogen-1fa7b6a29c61358cc2ca6f64cef4aa0e1a7ca74c.tar.xz
autogen-1fa7b6a29c61358cc2ca6f64cef4aa0e1a7ca74c.zip
Revert "mm: fail GFP_DMA allocations when ZONE_DMA is not configured"
This reverts commit a197b59ae6e8bee56fcef37ea2482dc08414e2ac. As rmk says: "Commit a197b59ae6e8 (mm: fail GFP_DMA allocations when ZONE_DMA is not configured) is causing regressions on ARM with various drivers which use GFP_DMA. The behaviour up until now has been to silently ignore that flag when CONFIG_ZONE_DMA is not enabled, and to allocate from the normal zone. However, as a result of the above commit, such allocations now fail which causes drivers to fail. These are regressions compared to the previous kernel version." so just revert it. Requested-by: Russell King <linux@arm.linux.org.uk> Acked-by: Andrew Morton <akpm@linux-foundation.org> Cc: David Rientjes <rientjes@google.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions