From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 4/5] of: silence of_diff output for negative indents
Date: Mon, 7 Feb 2022 08:56:20 +0100 [thread overview]
Message-ID: <20220207075621.1014381-4-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20220207075621.1014381-1-a.fatoum@pengutronix.de>
Negative indents just led to strange behavior so far. Repurpose them to
mean that the caller is not interested in console output. This makes
them useful for negative tests (Sanity check that two different nodes
are indeed different).
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
drivers/of/base.c | 15 +++++++++++++--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/drivers/of/base.c b/drivers/of/base.c
index 99be24254203..ffa79785f80e 100644
--- a/drivers/of/base.c
+++ b/drivers/of/base.c
@@ -2087,6 +2087,8 @@ int of_diff(struct device_node *a, struct device_node *b, int indent)
bp = of_find_property(b, ap->name, NULL);
if (!bp) {
diff++;
+ if (indent < 0)
+ continue;
of_print_parents(a, &printed);
printf("- ");
__of_print_property(ap, indent);
@@ -2095,6 +2097,8 @@ int of_diff(struct device_node *a, struct device_node *b, int indent)
if (ap->length != bp->length || memcmp(of_property_get_value(ap), of_property_get_value(bp), bp->length)) {
diff++;
+ if (indent < 0)
+ continue;
of_print_parents(a, &printed);
printf("- ");
__of_print_property(ap, indent);
@@ -2107,6 +2111,8 @@ int of_diff(struct device_node *a, struct device_node *b, int indent)
ap = of_find_property(a, bp->name, NULL);
if (!ap) {
diff++;
+ if (indent < 0)
+ continue;
of_print_parents(a, &printed);
printf("+ ");
__of_print_property(bp, indent);
@@ -2116,9 +2122,11 @@ int of_diff(struct device_node *a, struct device_node *b, int indent)
for_each_child_of_node(a, ca) {
cb = of_get_child_by_name(b, ca->name);
if (cb) {
- diff += of_diff(ca, cb, indent + 1);
+ diff += of_diff(ca, cb, indent >= 0 ? indent + 1 : indent);
} else {
diff++;
+ if (indent < 0)
+ continue;
of_print_parents(a, &printed);
__of_print_nodes(ca, indent, "- ");
}
@@ -2127,12 +2135,15 @@ int of_diff(struct device_node *a, struct device_node *b, int indent)
for_each_child_of_node(b, cb) {
if (!of_get_child_by_name(a, cb->name)) {
diff++;
+ if (indent < 0)
+ continue;
of_print_parents(a, &printed);
__of_print_nodes(cb, indent, "+ ");
}
}
- of_print_close(a, &printed);
+ if (indent >= 0)
+ of_print_close(a, &printed);
return diff;
}
--
2.30.2
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2022-02-07 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 7:56 [PATCH 1/5] test: self: printf: log skipped tests Ahmad Fatoum
2022-02-07 7:56 ` [PATCH 2/5] test: self: printf: add tests for %*ph prints Ahmad Fatoum
2022-02-07 7:56 ` [PATCH 3/5] of: report whether of_diff found differences in return code Ahmad Fatoum
2022-02-07 7:56 ` Ahmad Fatoum [this message]
2022-02-07 8:17 ` [PATCH 4/5] of: silence of_diff output for negative indents Sascha Hauer
2022-02-07 8:22 ` Sascha Hauer
2022-02-07 8:23 ` Ahmad Fatoum
2022-02-07 7:56 ` [PATCH 5/5] test: self: add device tree manipulation test Ahmad Fatoum
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=20220207075621.1014381-4-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@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