From:   Frank Rowand <frowand.list@gmail.com>
To:     Rob Herring <robh+dt@kernel.org>,
        Guenter Roeck <linux@roeck-us.net>,
        Jonathan Corbet <corbet@lwn.net>
Cc:     devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
        linux-doc@vger.kernel.org
Subject: [PATCH 0/2] of: unittest: option to allow tests that trigger kernel stack dump
Date:   Tue, 28 Feb 2023 19:21:14 -0600
Message-Id: <20230301012116.1488132-1-frowand.list@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Commit 74df14cd301a ("of: unittest: add node lifecycle tests") added
some tests that trigger a kernel stack dump.  Filtering the boot
messages with scripts/dtc/of_unittest_expect detects that the stack
dump is expected instead of being a test error.

Test beds might interpret the stack dumps as errors, resulting in
needless debugging and error reports.  These test beds are likely
to remove unittests due to these stack dumps. To avoid these problems,
have the unittest default to skip the tests that trigger a stack dump.

Add a kernel cmdline option to not skip those tests.  This option can
be used by testers who are able to interpret the stack dumps as not
an error.

Frank Rowand (2):
  of: unittest: option to allow tests that trigger kernel stack dump
  of: unittest: add of_unittest_stackdump to kernel documentation

 .../admin-guide/kernel-parameters.txt         |  4 ++
 drivers/of/unittest.c                         | 54 +++++++++++++++++--
 2 files changed, 55 insertions(+), 3 deletions(-)

-- 
Frank Rowand <frowand.list@gmail.com>