summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorCorey Minyard <cminyard@mvista.com>2017-08-19 01:32:03 +0300
committerCorey Minyard <cminyard@mvista.com>2017-09-28 00:03:45 +0300
commit1c9f98d1bfbd0696442f97fa7d43a727e1e16568 (patch)
treed8ec85252acaa934729502d072b832fc6906c815 /Documentation
parentb72fce52a14bbe0a94259a95032cf9dd1b3dd143 (diff)
downloadlinux-1c9f98d1bfbd0696442f97fa7d43a727e1e16568.tar.xz
ipmi: Make IPMI panic strings always available
They were set by config items, but people complained that they were never turned on. So have them always available and enabled by a module parameter. Signed-off-by: Corey Minyard <cminyard@mvista.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/IPMI.txt4
1 files changed, 3 insertions, 1 deletions
diff --git a/Documentation/IPMI.txt b/Documentation/IPMI.txt
index aa77a25a0940..5ef1047e2e66 100644
--- a/Documentation/IPMI.txt
+++ b/Documentation/IPMI.txt
@@ -81,7 +81,9 @@ If you want the driver to put an event into the event log on a panic,
enable the 'Generate a panic event to all BMCs on a panic' option. If
you want the whole panic string put into the event log using OEM
events, enable the 'Generate OEM events containing the panic string'
-option.
+option. You can also enable these dynamically by setting the module
+parameter named "panic_op" in the ipmi_msghandler module to "event"
+or "string". Setting that parameter to "none" disables this function.
Basic Design
------------