aboutsummaryrefslogtreecommitdiff
path: root/crypto
diff options
context:
space:
mode:
authorHeiko Carstens <heiko.carstens@de.ibm.com>2008-05-30 10:03:27 +0200
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2008-05-30 10:03:34 +0200
commit67060d9c1f5d91c917cc51bed464cb5638eaddbc (patch)
tree84a9f66567bcec141f80b0fbc9db995ac9323a50 /crypto
parentbebd9a455b2593ba6543b961bc82c43350c2d8d9 (diff)
[S390] Fix section mismatch warnings.
This fixes the last remaining section mismatch warnings in s390 architecture code. It reveals also a real bug introduced by... me with git commit 2069e978d5a6e7b45d58027e3de7f879b8c5e488 ("[S390] sparsemem vmemmap: initialize memmap.") Calling the generic vmemmap_alloc_block() function to get initialized memory is a nice idea, however that function is __meminit annotated and therefore the function might be gone if we try to call it later. This can happen if a DCSS segment gets added. So basically revert the patch and clear the memmap explicitly to fix the original bug. Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions