From: Rob Herring <robh@kernel.org>
To: frowand.list@gmail.com
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 1/1] of: unittest: update text of expected warnings
Date: Mon, 31 Jan 2022 08:35:59 -0600 [thread overview]
Message-ID: <Yffzz0xuJ44hO1Cy@robh.at.kernel.org> (raw)
In-Reply-To: <20220127192643.2534941-1-frowand.list@gmail.com>
On Thu, 27 Jan 2022 13:26:43 -0600, frowand.list@gmail.com wrote:
> From: Frank Rowand <frank.rowand@sony.com>
>
> The text of various warning messages triggered by unittest has
> changed. Update the text of expected warnings to match.
>
> The expected vs actual warnings are most easily seen by filtering
> the boot console messages with the of_unittest_expect program at
> https://github.com/frowand/dt_tools.git. The filter prefixes
> problem lines with '***', and prefixes lines that match expected
> errors with 'ok '. All other lines are prefixed with ' '.
> Unrelated lines have been deleted in the following examples.
>
> The mismatch appears as:
>
> -> ### dt-test ### start of unittest - you will see error messages
> OF: /testcase-data/phandle-tests/consumer-a: #phandle-cells = 3 found 1
> ** of_unittest_expect WARNING - not found ---> OF: /testcase-data/phandle-tests/consumer-a: #phandle-cells = 3 found -1
> OF: /testcase-data/phandle-tests/consumer-a: #phandle-cells = 3 found 1
> ** of_unittest_expect WARNING - not found ---> OF: /testcase-data/phandle-tests/consumer-a: #phandle-cells = 3 found -1
> OF: /testcase-data/phandle-tests/consumer-b: #phandle-cells = 2 found 1
> ** of_unittest_expect WARNING - not found ---> OF: /testcase-data/phandle-tests/consumer-b: #phandle-cells = 2 found -1
> platform testcase-data:testcase-device2: error -ENXIO: IRQ index 0 not found
> ** of_unittest_expect WARNING - not found ---> platform testcase-data:testcase-device2: IRQ index 0 not found
> -> ### dt-test ### end of unittest - 254 passed, 0 failed
> ** EXPECT statistics:
> **
> ** EXPECT found : 42
> ** EXPECT not found : 4
>
> With this commit applied, the mismatch is resolved:
>
> -> ### dt-test ### start of unittest - you will see error messages
> ok OF: /testcase-data/phandle-tests/consumer-a: #phandle-cells = 3 found 1
> ok OF: /testcase-data/phandle-tests/consumer-a: #phandle-cells = 3 found 1
> ok OF: /testcase-data/phandle-tests/consumer-b: #phandle-cells = 2 found 1
> ok platform testcase-data:testcase-device2: error -ENXIO: IRQ index 0 not found
> -> ### dt-test ### end of unittest - 254 passed, 0 failed
> ** EXPECT statistics:
> **
> ** EXPECT found : 46
> ** EXPECT not found : 0
>
> Fixes: 2043727c2882 ("driver core: platform: Make use of the helper function dev_err_probe()")
> Fixes: 94a4950a4acf ("of: base: Fix phandle argument length mismatch error message")
> Signed-off-by: Frank Rowand <frank.rowand@sony.com>
> ---
> drivers/of/unittest.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
Applied, thanks!
next prev parent reply other threads:[~2022-01-31 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 19:26 frowand.list
2022-01-31 14:35 ` Rob Herring [this message]
2022-01-31 15:04 ` Rob Herring
2022-02-01 18:23 ` 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=Yffzz0xuJ44hO1Cy@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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
Powered by JetHome