From: Jonathan Corbet <corbet@lwn.net>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: Miklos Szeredi <mszeredi@redhat.com>,
Rob Herring <robh@kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Richard Weinberger <richard@nod.at>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-doc@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"David S. Miller" <davem@davemloft.net>,
linux-mtd@lists.infradead.org,
"Tobin C. Harding" <tobin@kernel.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Jaskaran Singh <jaskaransingh7654321@gmail.com>,
"Daniel W. S. Almeida" <dwlsalmeida@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] docs: ubifs-authentication: fix Sphinx warning
Date: Wed, 19 Feb 2020 04:17:58 -0700 [thread overview]
Message-ID: <20200219041758.3b7316b8@lwn.net> (raw)
In-Reply-To: <20200214170833.25803-4-j.neuschaefer@gmx.net>
On Fri, 14 Feb 2020 18:08:07 +0100
Jonathan Neuschäfer <j.neuschaefer@gmx.net> wrote:
> This fixes the following warning:
>
> Documentation/filesystems/ubifs-authentication.rst:98: WARNING:
> Inline interpreted text or phrase reference start-string without end-string.
>
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
So this, IMO, should be fixed in patch #2, when you're touching the file
anyway. I don't see a lot of value in adding a warning to the docs build
then immediately removing it.
Also, please send a cover letter with multi-part sets like this so we
know what the overall objective is.
Note also that Mauro is also playing with this file (and ubifs.txt, which
really should be included as well) at the same time.
Thanks,
jon
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-02-19 11:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 17:08 [PATCH 1/4] MAINTAINERS: Add ubifs-authentication.rst to UBIFS Jonathan Neuschäfer
2020-02-14 17:08 ` [PATCH 2/4] docs: ubifs-authentication: Add a top-level heading Jonathan Neuschäfer
2020-02-14 17:08 ` [PATCH 3/4] docs: filesystems: link ubifs-authentication.rst Jonathan Neuschäfer
2020-02-14 17:08 ` [PATCH 4/4] docs: ubifs-authentication: fix Sphinx warning Jonathan Neuschäfer
2020-02-19 11:17 ` Jonathan Corbet [this message]
2020-02-21 15:59 ` Jonathan Neuschäfer
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=20200219041758.3b7316b8@lwn.net \
--to=corbet@lwn.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=davem@davemloft.net \
--cc=dwlsalmeida@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=j.neuschaefer@gmx.net \
--cc=jaskaransingh7654321@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mchehab+huawei@kernel.org \
--cc=mszeredi@redhat.com \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=stefanha@redhat.com \
--cc=tobin@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).