From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: fix coding-style.rst Sphinx warning
Date: Mon, 14 Jan 2019 08:32:14 -0700 [thread overview]
Message-ID: <20190114083214.54038927@lwn.net> (raw)
In-Reply-To: <bfeeb533-3909-30aa-a117-0b4179e8cfc3@infradead.org>
On Sun, 13 Jan 2019 19:28:58 -0800
Randy Dunlap <rdunlap@infradead.org> wrote:
> Fix Sphinx warning in coding-style.rst:
>
> Documentation/process/coding-style.rst:446: WARNING: Inline interpreted text or phrase reference start-string without end-string.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Applied, thanks.
jon
prev parent reply other threads:[~2019-01-14 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 3:28 Randy Dunlap
2019-01-14 15: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=20190114083214.54038927@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®