[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231208203128.GA2646347-robh@kernel.org>
Date: Fri, 8 Dec 2023 14:31:28 -0600
From: Rob Herring <robh@...nel.org>
To: Pintu Kumar <quic_pintu@...cinc.com>
Cc: linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
linux-mm@...ck.org, frowand.list@...il.com,
devicetree@...r.kernel.org, pintu.ping@...il.com
Subject: Re: [PATCH] of: reserved_mem: fix error log for reserved mem init
failure
On Wed, Dec 06, 2023 at 08:46:00PM +0530, Pintu Kumar wrote:
> During fdt_init_reserved_mem() when __reserved_mem_init_node()
> fail we are using pr_info to print error.
>
> So, if we change the loglevel to 4 (or below), this error
> message will be missed.
>
> Thus, change the pr_info to pr_err for fail case.
>
> Signed-off-by: Pintu Kumar <quic_pintu@...cinc.com>
> ---
> drivers/of/of_reserved_mem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/of/of_reserved_mem.c b/drivers/of/of_reserved_mem.c
> index 7ec94cfcbddb..473665e76b6f 100644
> --- a/drivers/of/of_reserved_mem.c
> +++ b/drivers/of/of_reserved_mem.c
> @@ -334,7 +334,7 @@ void __init fdt_init_reserved_mem(void)
> if (err == 0) {
> err = __reserved_mem_init_node(rmem);
> if (err != 0 && err != -ENOENT) {
> - pr_info("node %s compatible matching fail\n",
> + pr_err("node %s compatible matching fail\n",
Isn't the message just wrong. If compatible match fails, we return
ENOENT. The failure here would be from the init function.
> rmem->name);
> if (nomap)
> memblock_clear_nomap(rmem->base, rmem->size);
> --
> 2.17.1
>
Powered by blists - more mailing lists