Commit d3524bb5 authored by Kenneth Lee's avatar Kenneth Lee Committed by Greg Kroah-Hartman

nvmem: brcm_nvram: Use kzalloc for allocating only one element

Use kzalloc(...) rather than kcalloc(1, ...) because the number of
elements we are specifying in this case is 1, so kzalloc would
accomplish the same thing and we can simplify.
Signed-off-by: default avatarKenneth Lee <klee33@uw.edu>
Signed-off-by: default avatarSrinivas Kandagatla <srinivas.kandagatla@linaro.org>
Link: https://lore.kernel.org/r/20220916122100.170016-6-srinivas.kandagatla@linaro.orgSigned-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent ff1df188
...@@ -96,7 +96,7 @@ static int brcm_nvram_parse(struct brcm_nvram *priv) ...@@ -96,7 +96,7 @@ static int brcm_nvram_parse(struct brcm_nvram *priv)
len = le32_to_cpu(header.len); len = le32_to_cpu(header.len);
data = kcalloc(1, len, GFP_KERNEL); data = kzalloc(len, GFP_KERNEL);
memcpy_fromio(data, priv->base, len); memcpy_fromio(data, priv->base, len);
data[len - 1] = '\0'; data[len - 1] = '\0';
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment