From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Satoru Takeuchi <satoru.takeuchi@gmail.com>
Subject: [for-next][PATCH 2/2] ktest: Add documentation of CLOSE_CONSOLE_SIGNAL
Date: Tue, 03 Dec 2013 12:07:24 -0500 [thread overview]
Message-ID: <20131203170833.411600272@goodmis.org> (raw)
In-Reply-To: <20131203170722.102711563@goodmis.org>
[-- Attachment #1: 0002-ktest-Add-documentation-of-CLOSE_CONSOLE_SIGNAL.patch --]
[-- Type: text/plain, Size: 1032 bytes --]
From: "Steven Rostedt (Red Hat)" <rostedt@goodmis.org>
The sample.conf file needs to document all available options.
With the new CLOSE_CONSOE_SIGNAL option, it too needs to be
document.
Cc: Satoru Takeuchi <satoru.takeuchi@gmail.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
tools/testing/ktest/sample.conf | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/tools/testing/ktest/sample.conf b/tools/testing/ktest/sample.conf
index 0a290fb..2eb4bd2 100644
--- a/tools/testing/ktest/sample.conf
+++ b/tools/testing/ktest/sample.conf
@@ -328,6 +328,13 @@
# For a virtual machine with guest name "Guest".
#CONSOLE = virsh console Guest
+# Signal to send to kill console.
+# ktest.pl will create a child process to monitor the console.
+# When the console is finished, ktest will kill the child process
+# with this signal.
+# (default INT)
+#CLOSE_CONSOLE_SIGNAL = HUP
+
# Required version ending to differentiate the test
# from other linux builds on the system.
#LOCALVERSION = -test
--
1.8.4.rc3
prev parent reply other threads:[~2013-12-03 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 17:07 [for-next][PATCH 0/2] ktest: Added CLOSE_CONSOLE_SIGNAL Steven Rostedt
2013-12-03 17:07 ` [for-next][PATCH 1/2] ktest: Make the signal to terminate the console configurable Steven Rostedt
2013-12-03 17:07 ` Steven Rostedt [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=20131203170833.411600272@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=satoru.takeuchi@gmail.com \
/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