811-v6.1-0004-nvmem-brcm_nvram-Use-kzalloc-for-allocating-only-one.patch 1.0 KB

1234567891011121314151617181920212223242526272829
  1. From d3524bb5b9a0c567b853a0024526afe87dde01ed Mon Sep 17 00:00:00 2001
  2. From: Kenneth Lee <[email protected]>
  3. Date: Fri, 16 Sep 2022 13:20:52 +0100
  4. Subject: [PATCH] nvmem: brcm_nvram: Use kzalloc for allocating only one
  5. element
  6. Use kzalloc(...) rather than kcalloc(1, ...) because the number of
  7. elements we are specifying in this case is 1, so kzalloc would
  8. accomplish the same thing and we can simplify.
  9. Signed-off-by: Kenneth Lee <[email protected]>
  10. Signed-off-by: Srinivas Kandagatla <[email protected]>
  11. Link: https://lore.kernel.org/r/[email protected]
  12. Signed-off-by: Greg Kroah-Hartman <[email protected]>
  13. ---
  14. drivers/nvmem/brcm_nvram.c | 2 +-
  15. 1 file changed, 1 insertion(+), 1 deletion(-)
  16. --- a/drivers/nvmem/brcm_nvram.c
  17. +++ b/drivers/nvmem/brcm_nvram.c
  18. @@ -96,7 +96,7 @@ static int brcm_nvram_parse(struct brcm_
  19. len = le32_to_cpu(header.len);
  20. - data = kcalloc(1, len, GFP_KERNEL);
  21. + data = kzalloc(len, GFP_KERNEL);
  22. memcpy_fromio(data, priv->base, len);
  23. data[len - 1] = '\0';