linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Tom Zanussi <zanussi@kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/9] docs: trace: events.rst: convert some new stuff to ReST format
Date: Tue, 3 Mar 2020 15:48:26 -0500	[thread overview]
Message-ID: <20200303154826.2da803ed@gandalf.local.home> (raw)
In-Reply-To: <afbe367ccb7b9abcb9fab7bc5cb5e0686c105a53.1583250595.git.mchehab+huawei@kernel.org>

On Tue,  3 Mar 2020 16:50:31 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:

> Some new chapters were added to the documentation. This caused
> Sphinx to complain, as the literal blocks there are not properly
> tagged as such. Also, a new note added there doesn't follow
> the ReST format.
> 
> This fixes the following warnings:
> 
>     Documentation/trace/events.rst:589: WARNING: Definition list ends without a blank line; unexpected unindent.
>     Documentation/trace/events.rst:620: WARNING: Inline emphasis start-string without end-string.
>     Documentation/trace/events.rst:623: WARNING: Inline emphasis start-string without end-string.
>     Documentation/trace/events.rst:626: WARNING: Inline emphasis start-string without end-string.
>     Documentation/trace/events.rst:703: WARNING: Inline emphasis start-string without end-string.
>     Documentation/trace/events.rst:697: WARNING: Inline emphasis start-string without end-string.
>     Documentation/trace/events.rst:722: WARNING: Inline emphasis start-string without end-string.
>     Documentation/trace/events.rst:775: WARNING: Definition list ends without a blank line; unexpected unindent.
>     Documentation/trace/events.rst:814: WARNING: Inline emphasis start-string without end-string.
>     Documentation/trace/events.rst:817: WARNING: Inline emphasis start-string without end-string.
>     Documentation/trace/events.rst:820: WARNING: Inline emphasis start-string without end-string.
>     Documentation/trace/events.rst:823: WARNING: Inline emphasis start-string without end-string.
>     Documentation/trace/events.rst:826: WARNING: Inline emphasis start-string without end-string.
>     Documentation/trace/events.rst:829: WARNING: Inline emphasis start-string without end-string.
>     Documentation/trace/events.rst:832: WARNING: Inline emphasis start-string without end-string.
>     Documentation/trace/events.rst:844: WARNING: Unexpected indentation.
>     Documentation/trace/events.rst:845: WARNING: Block quote ends without a blank line; unexpected unindent.
>     Documentation/trace/events.rst:849: WARNING: Unexpected indentation.
>     Documentation/trace/events.rst:850: WARNING: Block quote ends without a blank line; unexpected unindent.
>     Documentation/trace/events.rst:883: WARNING: Inline emphasis start-string without end-string.
>     Documentation/trace/events.rst:886: WARNING: Inline emphasis start-string without end-string.
>     Documentation/trace/events.rst:889: WARNING: Inline emphasis start-string without end-string.
>     Documentation/trace/events.rst:895: WARNING: Bullet list ends without a blank line; unexpected unindent.
>     Documentation/trace/events.rst:895: WARNING: Inline emphasis start-string without end-string.
>     Documentation/trace/events.rst:968: WARNING: Inline emphasis start-string without end-string.
> 
> Fixes: 34ed63573b66 ("tracing: Documentation for in-kernel synthetic event API")
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
>

Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>

Jon, let me know if this applies to your tree. If not, I'll take it in mine.

-- Steve

  parent reply	other threads:[~2020-03-03 20:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 15:50 [PATCH 1/9] docs: trace: events.rst: convert some new stuff to ReST format Mauro Carvalho Chehab
2020-03-03 15:50 ` [PATCH 2/9] docs: watch_queue.rst: supress some Sphinx warnings Mauro Carvalho Chehab
2020-03-10 17:53   ` Jonathan Corbet
2020-03-10 18:29   ` David Howells
2020-03-11 12:11     ` Mauro Carvalho Chehab
2020-03-03 15:50 ` [PATCH 3/9] docs: dmaengine: provider.rst: get rid of some warnings Mauro Carvalho Chehab
2020-03-06 13:39   ` Vinod Koul
2020-03-03 15:50 ` [PATCH 4/9] docs: driver.rst: supress two ReSt warnings Mauro Carvalho Chehab
2020-03-10 17:54   ` Jonathan Corbet
2020-03-03 15:50 ` [PATCH 5/9] docs: gpio: driver.rst: don't mark literal blocks twice Mauro Carvalho Chehab
2020-03-04 14:20   ` Bartosz Golaszewski
2020-03-03 15:50 ` [PATCH 6/9] docs: translations: it: avoid duplicate refs at programming-language.rst Mauro Carvalho Chehab
2020-03-03 17:19   ` Nick Desaulniers
2020-03-04  8:34   ` Federico Vaga
2020-03-10 17:55   ` Jonathan Corbet
2020-03-03 15:50 ` [PATCH 7/9] docs: filesystems: fuse.rst: supress a Sphinx warning Mauro Carvalho Chehab
2020-03-10 17:55   ` Jonathan Corbet
2020-03-03 15:50 ` [PATCH 8/9] docs: perf: imx-ddr.rst: get rid of a warning Mauro Carvalho Chehab
2020-03-10 17:56   ` Jonathan Corbet
2020-03-03 15:50 ` [PATCH 9/9] docs: hw-vuln: tsx_async_abort.rst: get rid of an unused ref Mauro Carvalho Chehab
2020-03-10 17:57   ` Jonathan Corbet
2020-03-03 20:42 ` [PATCH 1/9] docs: trace: events.rst: convert some new stuff to ReST format Tom Zanussi
2020-03-03 20:48 ` Steven Rostedt [this message]
2020-03-10 17:49   ` Jonathan Corbet

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=20200303154826.2da803ed@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=zanussi@kernel.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).