linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Jerry Hoemann <jerry.hoemann@hpe.com>
Cc: linux@roeck-us.net, wim@linux-watchdog.org,
	linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] docs: watchdog: make htmldocs failed.
Date: Thu, 13 Jun 2019 06:57:02 -0300	[thread overview]
Message-ID: <20190613065554.1dd69b86@coco.lan> (raw)
In-Reply-To: <20190613000237.377-1-jerry.hoemann@hpe.com>

Em Wed, 12 Jun 2019 18:02:36 -0600
Jerry Hoemann <jerry.hoemann@hpe.com> escreveu:

> Guenter,
> 
> While making htmldocs from linux-staging.git watchdog-next, the
> build failed due what I think is a missing blank line after a header
> separator in:
> 
> 	Documentation/watchdog/watchdog-parameters.rst
> 
> I'm a newbie w.r.t. to the .rst file formats, but adding the blank
> lines got the "make htmldocs" to complete.

Yeah, Sphinx doesn't like to see things like:

------------
foo

as it will miss-interpret the <hr> tag. That usually cause a
severe error the parser, breaking the entire build.

> 
> 
> 
> 
> 
> 
> Jerry Hoemann (1):
>   docs: watchdog: Fix build error.
> 
>  Documentation/watchdog/watchdog-parameters.rst | 2 ++
>  1 file changed, 2 insertions(+)
> 



Thanks,
Mauro

      parent reply	other threads:[~2019-06-13 15:39 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 ` [PATCH 1/1] docs: watchdog: Fix build error Jerry Hoemann
2019-06-13  0:27   ` Guenter Roeck
2019-06-13  9:53   ` Mauro Carvalho Chehab
2019-06-13  9:57 ` Mauro Carvalho Chehab [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=20190613065554.1dd69b86@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=jerry.hoemann@hpe.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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 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).