[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqKrWQ1Jn2HCxFsPKYcPXbYUgyPytvc_YrS=sgkWHv1hZA@mail.gmail.com>
Date: Mon, 28 Feb 2022 15:24:32 -0600
From: Rob Herring <robh+dt@...nel.org>
To: Frank Rowand <frowand.list@...il.com>
Cc: devicetree@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] of: unittest: add program to process EXPECT messages
On Tue, Feb 1, 2022 at 12:14 PM <frowand.list@...il.com> wrote:
>
> From: Frank Rowand <frank.rowand@...y.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@...y.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.
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
Powered by blists - more mailing lists