From: Otto Sabart <ottosabart@seberm.com>
To: linux-doc@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>, trivial@kernel.org
Subject: [PATCH 0/8] Fix bad references to documentation files
Date: Wed, 2 Jan 2019 21:00:47 +0100 [thread overview]
Message-ID: <cover.1546457946.git.ottosabart@seberm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2157 bytes --]
This series of patches fixes multiple warnings
from `$ make refcheckdocs` output.
I am still not sure if it's good practise to send these changes in
a series (because they touch multiple trees) or as a single commit
because it is one "logical" change :).
I have no problem with squashing these commits (or some of them), just
let me know.
Otto Sabart (8):
MAINTAINERS: fix bad file reference into Documentation
doc: filesystems: fix bad references to nonexistent ext4.rst file
doc: bindings: fix bad reference to ARM CPU bindings
doc: trace: fix reference to cpuidle documentation file
doc: gpio-mvebu: fix broken reference to cp110-system-controller0.txt file
doc: scsi: remove reference to tmscsim.txt file
doc: pinctrl: fix bad reference to pinctrl.txt file
doc: fix multiple broken references
Documentation/admin-guide/kernel-parameters.txt | 2 +-
Documentation/cgroup-v1/blkio-controller.txt | 6 ++----
Documentation/devicetree/bindings/arm/cpu-capacity.txt | 2 +-
Documentation/devicetree/bindings/arm/idle-states.txt | 2 +-
Documentation/devicetree/bindings/arm/sp810.txt | 2 +-
Documentation/devicetree/bindings/arm/topology.txt | 2 +-
Documentation/devicetree/bindings/display/arm,pl11x.txt | 2 +-
Documentation/devicetree/bindings/gpio/gpio-mvebu.txt | 2 --
.../devicetree/bindings/interrupt-controller/arm,gic-v3.txt | 2 +-
Documentation/filesystems/dax.txt | 2 +-
Documentation/filesystems/ext2.txt | 2 +-
Documentation/trace/coresight-cpu-debug.txt | 2 +-
MAINTAINERS | 3 +--
arch/arm64/kernel/kexec_image.c | 2 +-
arch/x86/Kconfig | 2 +-
drivers/scsi/Kconfig | 2 --
include/linux/mfd/madera/pdata.h | 3 ++-
mm/Kconfig | 2 +-
18 files changed, 18 insertions(+), 24 deletions(-)
--
2.17.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2019-01-02 20:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 20:00 Otto Sabart [this message]
2019-01-02 20:01 ` [PATCH 1/8] MAINTAINERS: fix bad file reference into Documentation Otto Sabart
2019-01-02 20:01 ` [PATCH 2/8] doc: filesystems: fix bad references to nonexistent ext4.rst file Otto Sabart
2019-01-02 20:01 ` [PATCH 3/8] doc: bindings: fix bad reference to ARM CPU bindings Otto Sabart
2019-01-03 18:55 ` Otto Sabart
2019-01-03 20:53 ` Rob Herring
2019-01-04 9:26 ` Otto Sabart
2019-01-04 15:52 ` Rob Herring
2019-01-02 20:01 ` [PATCH 4/8] doc: trace: fix reference to cpuidle documentation file Otto Sabart
2019-01-02 20:02 ` [PATCH 5/8] doc: gpio-mvebu: fix broken reference to cp110-system-controller0.txt file Otto Sabart
2019-01-02 20:02 ` [PATCH 6/8] doc: scsi: remove reference to tmscsim.txt file Otto Sabart
2019-01-02 20:02 ` [PATCH 7/8] doc: pinctrl: fix bad reference to pinctrl.txt file Otto Sabart
2019-01-02 20:03 ` [PATCH 8/8] doc: fix multiple broken references Otto Sabart
2019-01-03 16:28 ` [PATCH 0/8] Fix bad references to documentation files Jonathan Corbet
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=cover.1546457946.git.ottosabart@seberm.com \
--to=ottosabart@seberm.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=trivial@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).