From: "Tobin C. Harding" <me@tobin.cc>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Tobin C. Harding" <tobin@kernel.org>,
Christopher Lameter <cl@linux.com>,
linux-doc@vger.kernel.org
Subject: [PATCH 0/3] docs: vm: Fix typo and build warnings
Date: Thu, 31 Jan 2019 15:06:20 +1100 [thread overview]
Message-ID: <20190131040623.15569-1-me@tobin.cc> (raw)
From: "Tobin C. Harding" <tobin@kernel.org>
Hi Jon,
This patchset started as a spelling typo fix to the SLUB docs, while
doing this I noticed a few build warnings for vm/ so build warning fixes
make up the rest of the set.
Patch 3 uses an underscore instead of a hyphen in the label name. This
clears the warning but I am not 100% sure this is the correct fix.
thanks,
Tobin.
Tobin C. Harding (3):
docs: Fix SLUB docs typo
docs: Add missing colon
docs: Use underscore not hyphen in label
Documentation/core-api/memory-allocation.rst | 2 +-
Documentation/vm/index.rst | 2 +-
Documentation/vm/slub.rst | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
--
2.20.1
next reply other threads:[~2019-01-31 4:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 4:06 Tobin C. Harding [this message]
2019-01-31 4:06 ` [PATCH 1/3] docs: Fix SLUB docs typo Tobin C. Harding
2019-01-31 9:30 ` Mike Rapoport
2019-01-31 4:06 ` [PATCH 2/3] docs: Add missing colon Tobin C. Harding
2019-01-31 9:30 ` Mike Rapoport
2019-01-31 4:06 ` [PATCH 3/3] docs: Use underscore not hyphen in label Tobin C. Harding
2019-01-31 9:27 ` Mike Rapoport
2019-01-31 20:56 ` Tobin C. Harding
2019-02-01 23:03 ` Jonathan Corbet
2019-02-02 14:32 ` Mike Rapoport
2019-02-03 23:20 ` Tobin C. Harding
2019-02-04 8:38 ` Mike Rapoport
2019-02-04 21:12 ` Tobin C. Harding
2019-02-04 23:03 ` Jonathan Corbet
2019-02-05 8:30 ` Markus Heiser
2019-02-06 4:27 ` Tobin C. Harding
2019-02-06 7:49 ` Markus Heiser
2019-02-06 20:28 ` 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=20190131040623.15569-1-me@tobin.cc \
--to=me@tobin.cc \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--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).