From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] of: unittest: add program to process EXPECT messages
Date: Mon, 28 Feb 2022 22:00:15 -0600 [thread overview]
Message-ID: <db542880-304a-f48b-2159-d0955841c8e9@gmail.com> (raw)
In-Reply-To: <CAL_JsqKrWQ1Jn2HCxFsPKYcPXbYUgyPytvc_YrS=sgkWHv1hZA@mail.gmail.com>
On 2/28/22 15:24, Rob Herring wrote:
> On Tue, Feb 1, 2022 at 12:14 PM <frowand.list@gmail.com> wrote:
>>
>> From: Frank Rowand <frank.rowand@sony.com>
>>
>> If unittest detects a problem it will print a warning or error message
>> to the console. Unittest also triggers warning and error messages from
>> other kernel code as a result of intentionally bad unittest data. This
>> has led to confusion as to whether the triggered messages are an
>> expected result of a test or whether there is a real problem that is
>> independent of unittest.
>>
>> EXPECT messages were added to unittest to report each triggered message
>> that is expected, resulting in verbose console output.
>>
>> scripts/dtc/of_unittest is a new program that processes the EXPECT
>> messages to determine whether the triggered messages occurred and
>> also removes the excess verbosity of the EXPECT messages. More
>> information is available from 'scripts/dtc/of_unittest_expect --help'.
>>
>> Signed-off-by: Frank Rowand <frank.rowand@sony.com>
>> ---
>> permissions for scripts/dtc/of_unittest should be 770
>
> Why? 755 is what the patch says and what most/all executables in the kernel are.
I based that on the permissions of other executables in scripts/dtc/
I do like 755 better, thanks for pointing out the wider population of
executables in the kernel.
-Frank
>
> Rob
>
>>
>> I will reply to this message with the usage message from
>> 'scripts/dtc/of_unittest_expect --help'.
>>
>> I will also reply with examples of raw and processed console logs.
>>
>> Documentation/devicetree/of_unittest.rst | 27 +-
>> scripts/dtc/of_unittest_expect | 408 +++++++++++++++++++++++
>> 2 files changed, 432 insertions(+), 3 deletions(-)
>> create mode 100755 scripts/dtc/of_unittest_expect
prev parent reply other threads:[~2022-03-01 4:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 18:14 [PATCH 1/1] of: unittest: add program to process EXPECT messages frowand.list
2022-02-01 18:27 ` Frank Rowand
2022-02-01 18:32 ` Frank Rowand
2022-02-01 18:37 ` Frank Rowand
2022-02-01 18:47 ` Frank Rowand
2022-02-01 18:49 ` Frank Rowand
2022-02-28 19:01 ` Frank Rowand
2022-02-28 21:24 ` Rob Herring
2022-03-01 4:00 ` Frank Rowand [this message]
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=db542880-304a-f48b-2159-d0955841c8e9@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).