diff options
author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2015-07-13 13:17:07 +0900 |
---|---|---|
committer | Simon Glass <sjg@chromium.org> | 2015-07-22 07:30:44 -0600 |
commit | 6b9f9eadffb5f64801746593784e12f07f2fadd0 (patch) | |
tree | a7175969f30db000d6d1bcc049e5f2a55e042314 /board/Marvell/db-88f6820-gp/db-88f6820-gp.c | |
parent | ebc3328cccc2bc7968fbd179e8e30fa1282b391a (diff) | |
download | u-boot-imx-6b9f9eadffb5f64801746593784e12f07f2fadd0.zip u-boot-imx-6b9f9eadffb5f64801746593784e12f07f2fadd0.tar.gz u-boot-imx-6b9f9eadffb5f64801746593784e12f07f2fadd0.tar.bz2 |
linux_compat: handle __GFP_ZERO in kmalloc()
Currently, kzalloc() returns zero-filled memory, while kmalloc()
simply ignores the second argument and never fills the memory
area with zeros.
I want kmalloc(size, __GFP_ZERO) to behave as kzalloc() does,
which will make it easier to add more memory allocator variants.
With the introduction of __GFP_ZERO flag, going forward, kzmalloc()
variants can fall back to kmalloc() enabling the __GFP_ZERO flag.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Heiko Schocher <hs@denx.de>
Acked-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Lukasz Majewski <l.majewski@samsung.com>
Diffstat (limited to 'board/Marvell/db-88f6820-gp/db-88f6820-gp.c')
0 files changed, 0 insertions, 0 deletions