From: Yu-Chien Peter Lin <peterlin@andestech.com>
To: opensbi@lists.infradead.org
Subject: [PATCH v2 3/6] lib: fix fdt_parse_plmt_node()
Date: Tue, 29 Nov 2022 10:42:02 +0000 [thread overview]
Message-ID: <Y4Xh+hoyaEORyc34@APC323> (raw)
In-Reply-To: <20221128091420.30391-4-heinrich.schuchardt@canonical.com>
On Mon, Nov 28, 2022 at 10:14:17AM +0100, Heinrich Schuchardt wrote:
> cpu_offset, cpu_intc_offset must be int to discover failed invocations of
> fdt_node_offset_by_phandle() or fdt_parent_offset().
>
> After determining cpu_offset we have to check this value and not
> cpu_intc_offset.
>
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Looks good to me.
Reviewed-by: Yu Chien Peter Lin <peterlin@andestech.com>
next prev parent reply other threads:[~2022-11-29 10:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 9:14 [PATCH v2 0/6] lib: fixes for fdt functions Heinrich Schuchardt
2022-11-28 9:14 ` [PATCH v2 1/6] lib: simplify fdt_parse_plmt_node() Heinrich Schuchardt
2022-12-02 15:55 ` Bin Meng
2022-11-28 9:14 ` [PATCH v2 2/6] lib: simplify fdt_parse_plicsw_node() Heinrich Schuchardt
2022-12-02 15:55 ` Bin Meng
2022-11-28 9:14 ` [PATCH v2 3/6] lib: fix fdt_parse_plmt_node() Heinrich Schuchardt
2022-11-28 12:52 ` Xiang W
2022-11-28 12:52 ` Xiang W
2022-11-29 10:42 ` Yu-Chien Peter Lin [this message]
2022-12-02 15:55 ` Bin Meng
2022-11-28 9:14 ` [PATCH v2 4/6] lib: fix fdt_parse_plicsw_node() Heinrich Schuchardt
2022-11-28 12:53 ` Xiang W
2022-11-28 12:53 ` Xiang W
2022-11-29 10:44 ` Yu-Chien Peter Lin
2022-12-02 15:55 ` Bin Meng
2022-11-28 9:14 ` [PATCH v2 5/6] lib: simplify fdt_translate_address() Heinrich Schuchardt
2022-12-02 15:55 ` Bin Meng
2022-11-28 9:14 ` [PATCH v2 6/6] lib: fix fdt_parse_aclint_node() Heinrich Schuchardt
2022-11-28 12:54 ` Xiang W
2022-11-28 12:54 ` Xiang W
2022-12-02 15:55 ` Bin Meng
2022-12-05 5:15 ` [PATCH v2 0/6] lib: fixes for fdt functions Anup Patel
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=Y4Xh+hoyaEORyc34@APC323 \
--to=peterlin@andestech.com \
--cc=opensbi@lists.infradead.org \
/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