linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <tobin@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Tobin C. Harding" <tobin@kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/4] docs: Fix various build warnings/errors
Date: Tue,  9 Apr 2019 10:43:55 +1000	[thread overview]
Message-ID: <20190409004359.29668-1-tobin@kernel.org> (raw)

Hi Jon,

Here are the first 4 patches from the v1 of this series that are still
useful when applied to the current docs-next branch.

Set does a few minor clean ups, nothing too amazing here.  Patch 2
removes three Sphinx build warnings:

Patch 3 is slightly subjective, holla at me (anyone) if you don't like it
and I'll remove it.

thanks,
Tobin.


Tobin C. Harding (4):
  docs: Fix spelling mistake
  docs: Add colon clearing sphinx warning
  docs: Remove unnecessary reference link title
  docs: Use reference to link to rst file

 Documentation/admin-guide/mm/numa_memory_policy.rst | 9 ++++-----
 Documentation/process/howto.rst                     | 2 +-
 Documentation/vm/numa.rst                           | 4 ++--
 include/linux/wait.h                                | 2 +-
 4 files changed, 8 insertions(+), 9 deletions(-)

-- 
2.21.0


             reply	other threads:[~2019-04-09  0:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09  0:43 Tobin C. Harding [this message]
2019-04-09  0:43 ` [PATCH v2 1/4] docs: Fix spelling mistake Tobin C. Harding
2019-04-09  0:43 ` [PATCH v2 2/4] docs: Add colon clearing sphinx warning Tobin C. Harding
2019-04-09  0:43 ` [PATCH v2 3/4] docs: Remove unnecessary reference link title Tobin C. Harding
2019-04-09 21:20   ` Jonathan Corbet
2019-04-09 23:21     ` Tobin C. Harding
2019-04-09  0:43 ` [PATCH v2 4/4] docs: Use reference to link to rst file Tobin C. Harding

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=20190409004359.29668-1-tobin@kernel.org \
    --to=tobin@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.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).