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 2/2] of: unittest: add of_unittest_stackdump to kernel documentation
Date: Tue, 28 Feb 2023 19:21:16 -0600 [thread overview]
Message-ID: <20230301012116.1488132-3-frowand.list@gmail.com> (raw)
In-Reply-To: <20230301012116.1488132-1-frowand.list@gmail.com>
Add new option of_unittest_stackdump to the documentation admin guide.
Signed-off-by: Frank Rowand <frowand.list@gmail.com>
---
Documentation/admin-guide/kernel-parameters.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index 6221a1d057dd..98c3fc7f4f72 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -3911,6 +3911,10 @@
This can be set from sysctl after boot.
See Documentation/admin-guide/sysctl/vm.rst for details.
+ of_unittest_stackdump [OF]
+ Do not skip OF unittests that trigger a kernel stack dump.
+ Default: skip the tests that trigger a kernel stack dump
+
ohci1394_dma=early [HW] enable debugging via the ohci1394 driver.
See Documentation/core-api/debugging-via-ohci1394.rst for more
info.
--
Frank Rowand <frowand.list@gmail.com>
prev parent reply other threads:[~2023-03-01 1:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 1:21 [PATCH 0/2] of: unittest: option to allow tests that trigger kernel stack dump Frank Rowand
2023-03-01 1:21 ` [PATCH 1/2] " Frank Rowand
2023-03-01 4:07 ` Guenter Roeck
2023-03-01 16:01 ` Frank Rowand
2023-03-24 21:43 ` Rob Herring
2023-03-26 0:56 ` Frank Rowand
2023-03-01 1:21 ` 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=20230301012116.1488132-3-frowand.list@gmail.com \
--to=frowand.list@gmail.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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).