From: Jonathan Corbet <corbet@lwn.net>
To: Vitor Massaru Iha <vitor@massaru.org>
Cc: linux-doc@vger.kernel.org, brendanhiggins@google.com,
linux-kernel@vger.kernel.org, mchehab@kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] [PATCH] docs: coresight: fix `make htmldocs` warning
Date: Tue, 5 May 2020 09:44:45 -0600 [thread overview]
Message-ID: <20200505094445.77248c5c@lwn.net> (raw)
In-Reply-To: <20200430203612.90404-1-vitor@massaru.org>
On Thu, 30 Apr 2020 17:36:12 -0300
Vitor Massaru Iha <vitor@massaru.org> wrote:
> Fix `make htmldocs` warning:
>
> Documentation/trace/coresight/coresight-ect.rst:2: WARNING: Explicit markup ends without a blank line; unexpected unindent.
>
> Signed-off-by: Vitor Massaru Iha <vitor@massaru.org>
> ---
> Documentation/trace/coresight/coresight-ect.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/trace/coresight/coresight-ect.rst b/Documentation/trace/coresight/coresight-ect.rst
> index ecc1e57012ef..a93e52abcf46 100644
> --- a/Documentation/trace/coresight/coresight-ect.rst
> +++ b/Documentation/trace/coresight/coresight-ect.rst
> @@ -1,4 +1,5 @@
> .. SPDX-License-Identifier: GPL-2.0
> +
> =============================================
> CoreSight Embedded Cross Trigger (CTI & CTM).
> =============================================
Applied, thanks.
jon
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
prev parent reply other threads:[~2020-05-05 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 20:36 [Linux-kernel-mentees] [PATCH] docs: coresight: fix `make htmldocs` warning Vitor Massaru Iha
2020-05-05 15:44 ` 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=20200505094445.77248c5c@lwn.net \
--to=corbet@lwn.net \
--cc=brendanhiggins@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=vitor@massaru.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).