From: Ashok Reddy Soma <ashok.reddy.soma@amd.com>
To: <u-boot@lists.denx.de>
Cc: <michal.simek@amd.com>, <peng.fan@nxp.com>,
<jh80.chung@samsung.com>, <git@amd.com>,
Algapally Santosh Sagar <santoshsagar.algapally@amd.com>,
Ashok Reddy Soma <ashok.reddy.soma@amd.com>
Subject: [PATCH v2 1/4] xilinx: common: Include header file to fix warning
Date: Thu, 19 Jan 2023 22:36:14 -0700 [thread overview]
Message-ID: <20230120053617.32463-2-ashok.reddy.soma@amd.com> (raw)
In-Reply-To: <20230120053617.32463-1-ashok.reddy.soma@amd.com>
From: Algapally Santosh Sagar <santoshsagar.algapally@amd.com>
Prototype is missing for board_get_usable_ram_top, which is pointed by
below sparse warning. Include init.h header file to fix this.
warning: no previous prototype for 'board_get_usable_ram_top'
[-Wmissing-prototypes].
Signed-off-by: Algapally Santosh Sagar <santoshsagar.algapally@amd.com>
Signed-off-by: Ashok Reddy Soma <ashok.reddy.soma@amd.com>
---
Changes in v2:
- Included header file instead of declaring prototype
- Modified description to reflect the same
board/xilinx/common/board.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/board/xilinx/common/board.c b/board/xilinx/common/board.c
index 59d87f2352..a5bd289776 100644
--- a/board/xilinx/common/board.c
+++ b/board/xilinx/common/board.c
@@ -9,6 +9,7 @@
#include <efi_loader.h>
#include <env.h>
#include <image.h>
+#include <init.h>
#include <lmb.h>
#include <log.h>
#include <asm/global_data.h>
--
2.17.1
next prev parent reply other threads:[~2023-01-20 5:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 5:36 [PATCH v2 0/4] Fix sparse warnings Ashok Reddy Soma
2023-01-20 5:36 ` Ashok Reddy Soma [this message]
2023-01-20 5:36 ` [PATCH v2 2/4] gpio: zynqmp: Handle error from get_gpio_modepin Ashok Reddy Soma
2023-01-20 5:36 ` [PATCH v2 3/4] xilinx: versal: Add missing header Ashok Reddy Soma
2023-01-20 5:36 ` [PATCH v2 4/4] drivers: mmc: Change datatype of tuning_loop_counter to int Ashok Reddy Soma
2023-01-27 8:48 ` [PATCH v2 0/4] Fix sparse warnings Michal Simek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230120053617.32463-2-ashok.reddy.soma@amd.com \
--to=ashok.reddy.soma@amd.com \
--cc=git@amd.com \
--cc=jh80.chung@samsung.com \
--cc=michal.simek@amd.com \
--cc=peng.fan@nxp.com \
--cc=santoshsagar.algapally@amd.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.