From: Corentin Labbe <clabbe@baylibre.com>
To: corbet@lwn.net, linux@roeck-us.net, wim@iguana.be
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-watchdog@vger.kernel.org,
Corentin Labbe <clabbe@baylibre.com>
Subject: [PATCH 1/3] documentation: watchdog: remove documentation of at32ap700x_wdt
Date: Thu, 1 Feb 2018 20:44:10 +0000 [thread overview]
Message-ID: <1517517852-35113-1-git-send-email-clabbe@baylibre.com> (raw)
Since at32ap700x_wdt is gone, no need to keep its documentation
Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
---
Documentation/watchdog/watchdog-parameters.txt | 5 -----
1 file changed, 5 deletions(-)
diff --git a/Documentation/watchdog/watchdog-parameters.txt b/Documentation/watchdog/watchdog-parameters.txt
index 6f9d7b418917..407d013b8643 100644
--- a/Documentation/watchdog/watchdog-parameters.txt
+++ b/Documentation/watchdog/watchdog-parameters.txt
@@ -40,11 +40,6 @@ margin: Watchdog margin in seconds (default=60)
nowayout: Disable watchdog shutdown on close
(default=kernel config parameter)
-------------------------------------------------
-at32ap700x_wdt:
-timeout: Timeout value. Limited to be 1 or 2 seconds. (default=2)
-nowayout: Watchdog cannot be stopped once started
- (default=kernel config parameter)
--------------------------------------------------
at91rm9200_wdt:
wdt_time: Watchdog time in seconds. (default=5)
nowayout: Watchdog cannot be stopped once started
--
2.13.6
next reply other threads:[~2018-02-01 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 20:44 Corentin Labbe [this message]
2018-02-01 20:44 ` [PATCH 2/3] documentation: watchdog: remove documentation for ixp2000 Corentin Labbe
2018-02-01 22:31 ` Guenter Roeck
2018-02-01 20:44 ` [PATCH 3/3] documentation: watchdog: remove documentation of w83697hf_wdt/w83697ug_wdt Corentin Labbe
2018-02-01 22:31 ` Guenter Roeck
2018-02-01 22:30 ` [PATCH 1/3] documentation: watchdog: remove documentation of at32ap700x_wdt Guenter Roeck
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=1517517852-35113-1-git-send-email-clabbe@baylibre.com \
--to=clabbe@baylibre.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@iguana.be \
/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).