linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Andreas Ziegler <andreas.ziegler@fau.de>,
	Lecopzer Chen <lecopzer.chen@mediatek.com>
Subject: Re: [PATCH 2/6] docs: trace: add a missing blank line
Date: Tue, 18 Jun 2019 14:59:54 -0400	[thread overview]
Message-ID: <20190618145954.308e8ec3@gandalf.local.home> (raw)
In-Reply-To: <91f90c10c12c6a2f6fb90fc0f9115fbd8dd73848.1560883872.git.mchehab+samsung@kernel.org>

On Tue, 18 Jun 2019 15:51:18 -0300
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:

> Sphinx expects a blank line after a literal block markup.
> 
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>

For the two tracing patches (1 and 2).

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

-- Steve

> ---
>  Documentation/trace/kprobetrace.rst | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/trace/kprobetrace.rst b/Documentation/trace/kprobetrace.rst
> index 3d162d432a3c..caa0a8ba081e 100644
> --- a/Documentation/trace/kprobetrace.rst
> +++ b/Documentation/trace/kprobetrace.rst
> @@ -228,6 +228,7 @@ events, you need to enable it.
>  
>  Use the following command to start tracing in an interval.
>  ::
> +
>      # echo 1 > tracing_on
>      Open something...
>      # echo 0 > tracing_on


  reply	other threads:[~2019-06-18 18:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18 18:51 [PATCH 1/6] docs: trace: fix a broken label Mauro Carvalho Chehab
2019-06-18 18:51 ` [PATCH 2/6] docs: trace: add a missing blank line Mauro Carvalho Chehab
2019-06-18 18:59   ` Steven Rostedt [this message]
2019-06-19 15:08   ` Masami Hiramatsu
2019-06-20 20:07   ` Jonathan Corbet
2019-06-18 18:51 ` [PATCH 3/6] lib: list_sort.c: add a blank line to avoid kernel-doc warnings Mauro Carvalho Chehab
2019-06-20 20:07   ` Jonathan Corbet
2019-06-18 18:51 ` [PATCH 4/6] time: hrtimer: use a bullet for the returns bullet list Mauro Carvalho Chehab
2019-06-20 20:02   ` Jonathan Corbet
2019-06-20 20:16     ` Mauro Carvalho Chehab
2019-06-23 10:32       ` Thomas Gleixner
2019-06-18 18:51 ` [PATCH 5/6] docs: signal: fix a kernel-doc markup Mauro Carvalho Chehab
2019-06-18 18:51 ` [PATCH 6/6] drivers: base/node.c: fixes a kernel-doc markups Mauro Carvalho Chehab
2019-06-18 18:55   ` [PATCH v2 " Mauro Carvalho Chehab
2019-06-19 15:09 ` [PATCH 1/6] docs: trace: fix a broken label Masami Hiramatsu
2019-06-20 20:06 ` 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=20190618145954.308e8ec3@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=andreas.ziegler@fau.de \
    --cc=corbet@lwn.net \
    --cc=lecopzer.chen@mediatek.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=mchehab@infradead.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@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).