From: Jerry Hoemann <jerry.hoemann@hpe.com>
To: linux@roeck-us.net
Cc: wim@linux-watchdog.org, mchehab+samsung@kernel.org,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
Jerry Hoemann <jerry.hoemann@hpe.com>
Subject: [PATCH 1/1] docs: watchdog: Fix build error.
Date: Wed, 12 Jun 2019 18:02:37 -0600 [thread overview]
Message-ID: <20190613000237.377-2-jerry.hoemann@hpe.com> (raw)
In-Reply-To: <20190613000237.377-1-jerry.hoemann@hpe.com>
make htmldocs fails due to missing blank line following header.
Signed-off-by: Jerry Hoemann <jerry.hoemann@hpe.com>
---
Documentation/watchdog/watchdog-parameters.rst | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/watchdog/watchdog-parameters.rst b/Documentation/watchdog/watchdog-parameters.rst
index 01023382ea73..a3985cc5aeda 100644
--- a/Documentation/watchdog/watchdog-parameters.rst
+++ b/Documentation/watchdog/watchdog-parameters.rst
@@ -12,6 +12,7 @@ providing kernel parameters for builtin drivers versus loadable
modules.
-------------------------------------------------
+
watchdog core:
open_timeout:
Maximum time, in seconds, for which the watchdog framework will take
@@ -22,6 +23,7 @@ watchdog core:
fallback logic in the bootloader to try something else.
-------------------------------------------------
+
acquirewdt:
wdt_stop:
Acquire WDT 'stop' io port (default 0x43)
--
2.20.1
next prev parent reply other threads:[~2019-06-13 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 0:02 [PATCH 0/1] docs: watchdog: make htmldocs failed Jerry Hoemann
2019-06-13 0:02 ` Jerry Hoemann [this message]
2019-06-13 0:27 ` [PATCH 1/1] docs: watchdog: Fix build error Guenter Roeck
2019-06-13 9:53 ` Mauro Carvalho Chehab
2019-06-13 9:57 ` [PATCH 0/1] docs: watchdog: make htmldocs failed Mauro Carvalho Chehab
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=20190613000237.377-2-jerry.hoemann@hpe.com \
--to=jerry.hoemann@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mchehab+samsung@kernel.org \
--cc=wim@linux-watchdog.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.