Linux-Watchdog Archive on lore.kernel.org
 help / color / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Jerry Hoemann <jerry.hoemann@hpe.com>
Cc: wim@linux-watchdog.org, mchehab+samsung@kernel.org,
	linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] docs: watchdog: Fix build error.
Date: Wed, 12 Jun 2019 17:27:00 -0700
Message-ID: <20190613002700.GA1284@roeck-us.net> (raw)
In-Reply-To: <20190613000237.377-2-jerry.hoemann@hpe.com>

On Wed, Jun 12, 2019 at 06:02:37PM -0600, Jerry Hoemann wrote:
> make htmldocs fails due to missing blank line following header.
> 
> Signed-off-by: Jerry Hoemann <jerry.hoemann@hpe.com>

Reviewed-by: Guenter Roeck <linux@roeck-us.net>

> ---
>  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
> 

  reply index

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 ` [PATCH 1/1] docs: watchdog: Fix build error Jerry Hoemann
2019-06-13  0:27   ` Guenter Roeck [this message]
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 publically 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=20190613002700.GA1284@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jerry.hoemann@hpe.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --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

Linux-Watchdog Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-watchdog/0 linux-watchdog/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-watchdog linux-watchdog/ https://lore.kernel.org/linux-watchdog \
		linux-watchdog@vger.kernel.org linux-watchdog@archiver.kernel.org
	public-inbox-index linux-watchdog


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-watchdog


AGPL code for this site: git clone https://public-inbox.org/ public-inbox