From: Jonathan Corbet <corbet@lwn.net>
To: Sameer Rahmani <lxsameer@gnu.org>
Cc: linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: build warnings related to missing blank lines after explicit markups has been fixed
Date: Wed, 5 Feb 2020 10:32:03 -0700 [thread overview]
Message-ID: <20200205103203.39012f24@lwn.net> (raw)
In-Reply-To: <20200203201543.24834-1-lxsameer@gnu.org>
On Mon, 3 Feb 2020 20:15:43 +0000
Sameer Rahmani <lxsameer@gnu.org> wrote:
> Fix for several documentation build warnings related to missing blank lines
> after explicit mark up.
>
> Exact warning message:
> WARNING: Explicit markup ends without a blank line; unexpected unindent.
>
> Signed-off-by: Sameer Rahmani <lxsameer@gnu.org>
> ---
> Documentation/doc-guide/contributing.rst | 1 +
> Documentation/doc-guide/maintainer-profile.rst | 1 +
> Documentation/trace/kprobetrace.rst | 2 +-
> 3 files changed, 3 insertions(+), 1 deletion(-)
Argh. I ask people to look for warnings, then add two
myself...embarrassing. Many thanks for fixing these, applied.
If I'm not mistaken, this is your first accepted kernel patch.
Congratulations, and I'm glad you started with documentation!
jon
prev parent reply other threads:[~2020-02-05 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 20:15 [PATCH] Documentation: build warnings related to missing blank lines after explicit markups has been fixed Sameer Rahmani
2020-02-05 17:32 ` 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=20200205103203.39012f24@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=lxsameer@gnu.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).