From: Rob Herring <robh@kernel.org>
To: frowand.list@gmail.com
Cc: "Clément Léger" <clement.leger@bootlin.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Lizhi Hou" <lizhi.hou@xilinx.com>,
"Allan Nielsen" <allan.nielsen@microchip.com>,
"Horatiu Vultur" <horatiu.vultur@microchip.com>,
"Steen Hegelund" <steen.hegelund@microchip.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH 2/2] of: unittest: treat missing of_root as error instead of fixing up
Date: Tue, 28 Jun 2022 08:36:59 -0600 [thread overview]
Message-ID: <20220628143659.GA424332-robh@kernel.org> (raw)
In-Reply-To: <20220624034327.2542112-3-frowand.list@gmail.com>
On Thu, Jun 23, 2022 at 10:43:27PM -0500, frowand.list@gmail.com wrote:
> From: Frank Rowand <frank.rowand@sony.com>
>
> setup_of() now ensures that of_root node is populated with the
> root of a default devicetree. Remove the unittest code that
> created of_root if it was missing. Verify that of_root is
> valid before attempting to attach the testcase-data subtree.
What happened with the formatting here?
>
> Signed-off-by: Frank Rowand <frank.rowand@sony.com>
> ---
> drivers/of/unittest.c | 16 ++++++----------
> 1 file changed, 6 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/of/unittest.c b/drivers/of/unittest.c
> index 7f6bba18c515..9d106998c1f2 100644
> --- a/drivers/of/unittest.c
> +++ b/drivers/of/unittest.c
> @@ -1469,20 +1469,16 @@ static int __init unittest_data_add(void)
> return -EINVAL;
> }
>
> - if (!of_root) {
> - of_root = unittest_data_node;
> - for_each_of_allnodes(np)
> - __of_attach_node_sysfs(np);
> - of_aliases = of_find_node_by_path("/aliases");
> - of_chosen = of_find_node_by_path("/chosen");
> - of_overlay_mutex_unlock();
> - return 0;
> - }
> -
> EXPECT_BEGIN(KERN_INFO,
> "Duplicate name in testcase-data, renamed to \"duplicate-name#1\"");
>
> /* attach the sub-tree to live tree */
> + if (!of_root) {
> + pr_warn("%s: no live tree to attach sub-tree\n", __func__);
> + kfree(unittest_data);
> + return -ENODEV;
> + }
> +
> np = unittest_data_node->child;
> while (np) {
> struct device_node *next = np->sibling;
> --
> Frank Rowand <frank.rowand@sony.com>
>
>
next prev parent reply other threads:[~2022-06-28 14:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 3:43 [PATCH 0/2] of: populate of_root_node if not set (alternate) frowand.list
2022-06-24 3:43 ` [PATCH 1/2] of: create of_root if no dtb provided frowand.list
2022-06-24 12:13 ` Clément Léger
2022-06-24 16:44 ` Frank Rowand
2022-06-27 9:11 ` Clément Léger
2022-06-27 17:59 ` Rob Herring
2022-10-11 7:26 ` Clément Léger
2023-01-09 8:40 ` Clément Léger
2023-01-10 6:27 ` Frank Rowand
2023-01-10 8:12 ` Clément Léger
2023-01-24 14:34 ` Frank Rowand
2023-02-20 11:15 ` Clément Léger
2023-02-20 18:51 ` Frank Rowand
2022-06-24 3:43 ` [PATCH 2/2] of: unittest: treat missing of_root as error instead of fixing up frowand.list
2022-06-28 14:36 ` Rob Herring [this message]
2022-06-28 19:34 ` Frank Rowand
-- strict thread matches above, loose matches on Subject: below --
2023-02-22 3:54 [PATCH 0/2] of: populate of_root_node if not set (alternate) Frank Rowand
2023-02-22 3:54 ` [PATCH 2/2] of: unittest: treat missing of_root as error instead of fixing up Frank Rowand
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=20220628143659.GA424332-robh@kernel.org \
--to=robh@kernel.org \
--cc=allan.nielsen@microchip.com \
--cc=clement.leger@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.hou@xilinx.com \
--cc=steen.hegelund@microchip.com \
--cc=thomas.petazzoni@bootlin.com \
/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