From: Martin Walch <walch.martin@web.de>
To: Jonathan Corbet <corbet@lwn.net>,
Federico Vaga <federico.vaga@vaga.pv.it>
Cc: Harry Wei <harryxiyou@gmail.com>,
Alex Shi <alex.shi@linux.alibaba.com>,
Eric Biggers <ebiggers@kernel.org>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Mark Brown <broonie@kernel.org>,
linux-doc@vger.kernel.org, Jiri Kosina <trivial@kernel.org>
Subject: Re: [PATCH v2] Documentation: Fix some broken references
Date: Mon, 04 May 2020 16:50:30 +0200 [thread overview]
Message-ID: <8978478.eNJFYEL58v@tacticalops> (raw)
In-Reply-To: <12511156.uLZWGnKmhe@harkonnen>
From a4c8874109227995524ee598e84404edcb78cf64 Mon Sep 17 00:00:00 2001
From: Martin Walch <walch.martin@web.de>
Date: Mon, 4 May 2020 16:36:47 +0200
Subject: [PATCH] Documentation: Fix some broken references
filesystems/fsverity.rst:
* device-mapper/verity.txt is now admin-guide/device-mapper/verity.rst
filesystems/ubifs-authentication.rst:
* device-mapper has moved into admin-guide
Signed-off-by: Martin Walch <walch.martin@web.de>
---
On Monday, May 4, 2020 14:13:26 CEST Federico Vaga wrote:
> these changes (submit-checklist) are already in the docs-next branch
Sorry, I missed that. Thank you for pointing out.
This is a reduced patched without conflicts with docs-next.
Documentation/filesystems/fsverity.rst | 2 +-
Documentation/filesystems/ubifs-authentication.rst | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/filesystems/fsverity.rst b/Documentation/filesystems/fsverity.rst
index a95536b6443c..6cfa671c90d7 100644
--- a/Documentation/filesystems/fsverity.rst
+++ b/Documentation/filesystems/fsverity.rst
@@ -16,7 +16,7 @@ filesystems. Like fscrypt, not too much filesystem-specific code is
needed to support fs-verity.
fs-verity is similar to `dm-verity
-<https://www.kernel.org/doc/Documentation/device-mapper/verity.txt>`_
+<https://www.kernel.org/doc/Documentation/admin-guide/device-mapper/verity.rst>`_
but works on files rather than block devices. On regular files on
filesystems supporting fs-verity, userspace can execute an ioctl that
causes the filesystem to build a Merkle tree for the file and persist
diff --git a/Documentation/filesystems/ubifs-authentication.rst b/Documentation/filesystems/ubifs-authentication.rst
index 16efd729bf7c..960b690f5f44 100644
--- a/Documentation/filesystems/ubifs-authentication.rst
+++ b/Documentation/filesystems/ubifs-authentication.rst
@@ -437,9 +437,9 @@ References
[DMC-CBC-ATTACK] http://www.jakoblell.com/blog/2013/12/22/practical-malleability-attack-against-cbc-encrypted-luks-partitions/
-[DM-INTEGRITY] https://www.kernel.org/doc/Documentation/device-mapper/dm-integrity.rst
+[DM-INTEGRITY] https://www.kernel.org/doc/Documentation/admin-guide/device-mapper/dm-integrity.rst
-[DM-VERITY] https://www.kernel.org/doc/Documentation/device-mapper/verity.rst
+[DM-VERITY] https://www.kernel.org/doc/Documentation/admin-guide/device-mapper/verity.rst
[FSCRYPT-POLICY2] https://www.spinics.net/lists/linux-ext4/msg58710.html
--
2.26.2
prev parent reply other threads:[~2020-05-04 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 10:59 [PATCH] Documentation: Fix some broken references Martin Walch
2020-05-04 12:13 ` Federico Vaga
2020-05-04 14:50 ` Martin Walch [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=8978478.eNJFYEL58v@tacticalops \
--to=walch.martin@web.de \
--cc=alex.shi@linux.alibaba.com \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=ebiggers@kernel.org \
--cc=federico.vaga@vaga.pv.it \
--cc=harryxiyou@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=trivial@kernel.org \
--cc=tytso@mit.edu \
/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).