From: Rob Herring <robh@kernel.org>
To: Frank Rowand <frowand.list@gmail.com>,
"Enrico Weigelt, metux IT consult" <info@metux.net>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Petr Mladek <pmladek@suse.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 1/6] of: unittest: Fix EXPECT for parse_phandle_with_args_map() test
Date: Fri, 04 Aug 2023 16:41:51 -0600 [thread overview]
Message-ID: <20230801-dt-changeset-fixes-v2-1-c2b701579dee@kernel.org> (raw)
In-Reply-To: <20230801-dt-changeset-fixes-v2-0-c2b701579dee@kernel.org>
Commit 12e17243d8a1 ("of: base: improve error msg in
of_phandle_iterator_next()") added printing of the phandle value on
error, but failed to update the unittest.
Fixes: 12e17243d8a1 ("of: base: improve error msg in of_phandle_iterator_next()")
Signed-off-by: Rob Herring <robh@kernel.org>
---
drivers/of/unittest.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/of/unittest.c b/drivers/of/unittest.c
index e5b0eea8011c..d943bf87c94d 100644
--- a/drivers/of/unittest.c
+++ b/drivers/of/unittest.c
@@ -664,12 +664,12 @@ static void __init of_unittest_parse_phandle_with_args_map(void)
memset(&args, 0, sizeof(args));
EXPECT_BEGIN(KERN_INFO,
- "OF: /testcase-data/phandle-tests/consumer-b: could not find phandle");
+ "OF: /testcase-data/phandle-tests/consumer-b: could not find phandle 12345678");
rc = of_parse_phandle_with_args_map(np, "phandle-list-bad-phandle",
"phandle", 0, &args);
EXPECT_END(KERN_INFO,
- "OF: /testcase-data/phandle-tests/consumer-b: could not find phandle");
+ "OF: /testcase-data/phandle-tests/consumer-b: could not find phandle 12345678");
unittest(rc == -EINVAL, "expected:%i got:%i\n", -EINVAL, rc);
--
2.40.1
next prev parent reply other threads:[~2023-08-04 22:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 22:41 [PATCH v2 0/6] dt: changeset fixes and cleanups Rob Herring
2023-08-04 22:41 ` Rob Herring [this message]
2023-08-18 15:27 ` [PATCH v2 1/6] of: unittest: Fix EXPECT for parse_phandle_with_args_map() test Geert Uytterhoeven
2023-08-04 22:41 ` [PATCH v2 2/6] of: dynamic: Refactor action prints to not use "%pOF" inside devtree_lock Rob Herring
2023-08-07 15:30 ` Andy Shevchenko
2023-08-18 15:36 ` Geert Uytterhoeven
2023-08-18 16:16 ` Rob Herring
2023-08-18 17:36 ` Geert Uytterhoeven
2023-08-18 18:13 ` Rob Herring
2023-08-04 22:41 ` [PATCH v2 3/6] of: dynamic: Refactor changeset action printing to common helpers Rob Herring
2023-08-04 22:41 ` [PATCH v2 4/6] of: dynamic: Fix race in getting old property when updating property Rob Herring
2023-08-04 22:41 ` [PATCH v2 5/6] of: dynamic: Move dead property list check into property add/update functions Rob Herring
2023-08-07 15:37 ` Andy Shevchenko
2023-08-17 17:09 ` Rob Herring
2023-08-17 17:15 ` Andy Shevchenko
2023-08-04 22:41 ` [PATCH v2 6/6] of: Refactor node and property manipulation function locking Rob Herring
2023-08-07 15:40 ` Andy Shevchenko
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=20230801-dt-changeset-fixes-v2-1-c2b701579dee@kernel.org \
--to=robh@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=info@metux.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rafael.j.wysocki@intel.com \
--cc=sakari.ailus@linux.intel.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;
as well as URLs for NNTP newsgroup(s).