From: Jonathan Corbet <corbet@lwn.net>
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,
Masami Hiramatsu <mhiramat@kernel.org>,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>,
Andreas Ziegler <andreas.ziegler@fau.de>,
Lecopzer Chen <lecopzer.chen@mediatek.com>
Subject: Re: [PATCH 1/6] docs: trace: fix a broken label
Date: Thu, 20 Jun 2019 14:06:51 -0600 [thread overview]
Message-ID: <20190620140651.393e4680@lwn.net> (raw)
In-Reply-To: <a83ea390bc28784518fce772b4c961ea1c976f14.1560883872.git.mchehab+samsung@kernel.org>
On Tue, 18 Jun 2019 15:51:17 -0300
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> Sphinx warnings about his:
>
> Documentation/trace/kprobetrace.rst:68: WARNING: undefined label: user_mem_access (if the link has no caption the label must precede a section header)
>
> The problem is quite simple: Sphinx wants a blank line after
> references.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> ---
> Documentation/trace/kprobetrace.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/trace/kprobetrace.rst b/Documentation/trace/kprobetrace.rst
> index b729b40a5ba5..3d162d432a3c 100644
> --- a/Documentation/trace/kprobetrace.rst
> +++ b/Documentation/trace/kprobetrace.rst
> @@ -96,6 +96,7 @@ which shows given pointer in "symbol+offset" style.
> For $comm, the default type is "string"; any other type is invalid.
>
> .. _user_mem_access:
This one doesn't apply to docs-next; it should probably go through
whichever tree introduced the issue into linux-next.
Thanks,
jon
prev parent reply other threads:[~2019-06-20 20:06 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
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 [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=20190620140651.393e4680@lwn.net \
--to=corbet@lwn.net \
--cc=andreas.ziegler@fau.de \
--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=rostedt@goodmis.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).