public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Leo Liang <ycliang@andestech.com>
To: Chanho Park <chanho61.park@samsung.com>
Cc: Rick Chen <rick@andestech.com>, Simon Glass <sjg@chromium.org>,
	<u-boot@lists.denx.de>
Subject: Re: [PATCH v2 1/3] riscv: bootstage: correct bootstage_report guard
Date: Mon, 4 Sep 2023 14:41:58 +0800	[thread overview]
Message-ID: <ZPV8NvEjpy6JKqpl@swlinux02> (raw)
In-Reply-To: <20230828094938.2061606-2-chanho61.park@samsung.com>

On Mon, Aug 28, 2023 at 06:49:36PM +0900, Chanho Park wrote:
> Below warning can be occurred when CONFIG_BOOTSTAGE and
> !CONFIG_SPL_BOOTSTAGE. It should be guarded by using CONFIG_IS_ENABLED
> for SPL build.
> 
> arch/riscv/lib/bootm.c:46:9: warning: implicit declaration of
> function 'bootstage_report'
>    46 |         bootstage_report();
>       |         ^~~~~~~~~~~~~~~~
>       |         bootstage_error
> 
> Signed-off-by: Chanho Park <chanho61.park@samsung.com>
> ---
>  arch/riscv/lib/bootm.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>

  reply	other threads:[~2023-09-04  6:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230828094952epcas2p31c71a57ef3486cbd75f605057cc8085f@epcas2p3.samsung.com>
2023-08-28  9:49 ` [PATCH v2 0/3] bootstage support for risc-v Chanho Park
2023-08-28  9:49   ` [PATCH v2 1/3] riscv: bootstage: correct bootstage_report guard Chanho Park
2023-09-04  6:41     ` Leo Liang [this message]
2023-08-28  9:49   ` [PATCH v2 2/3] riscv: timer: add timer_get_boot_us for BOOTSTAGE Chanho Park
2023-09-04  7:01     ` Leo Liang
2023-09-04  7:41       ` Chanho Park
2023-08-28  9:49   ` [PATCH v2 3/3] timer: riscv_aclint_timer: " Chanho Park
2023-09-04  7:02     ` Leo Liang
2023-09-04  7:42       ` Chanho Park
2023-09-04 16:48     ` Simon Glass
2023-09-05  5:02       ` Chanho Park

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=ZPV8NvEjpy6JKqpl@swlinux02 \
    --to=ycliang@andestech.com \
    --cc=chanho61.park@samsung.com \
    --cc=rick@andestech.com \
    --cc=sjg@chromium.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox