mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Saeger <tom.saeger@oracle.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Tom Saeger <tom.saeger@oracle.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 4/8] Documentation: fix security related doc refs
Date: Tue, 10 Oct 2017 12:36:30 -0500	[thread overview]
Message-ID: <cdf92bcf04d0c065308c8590fca1cdb7376fb373.1507653970.git.tom.saeger@oracle.com> (raw)
In-Reply-To: <cover.1507653969.git.tom.saeger@oracle.com>

Make security document refs valid.

Signed-off-by: Tom Saeger <tom.saeger@oracle.com>
---
 Documentation/ABI/testing/evm               | 4 ++--
 Documentation/security/LSM.rst              | 2 +-
 Documentation/security/credentials.rst      | 2 +-
 Documentation/security/keys/request-key.rst | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/Documentation/ABI/testing/evm b/Documentation/ABI/testing/evm
index 8374d4557e5d..ca622c9aa24c 100644
--- a/Documentation/ABI/testing/evm
+++ b/Documentation/ABI/testing/evm
@@ -18,6 +18,6 @@ Description:
 		in the initramfs, which has already been measured as part
 		of the trusted boot.  For more information on creating and
 		loading existing trusted/encrypted keys, refer to:
-		Documentation/keys-trusted-encrypted.txt.  (A sample dracut
-		patch, which loads the trusted/encrypted key and enables
+		Documentation/security/keys/trusted-encrypted.rst.  (A sample
+		dracut patch, which loads the trusted/encrypted key and enables
 		EVM, is available from http://linux-ima.sourceforge.net/#EVM.)
diff --git a/Documentation/security/LSM.rst b/Documentation/security/LSM.rst
index d75778b0fa10..98522e0e1ee2 100644
--- a/Documentation/security/LSM.rst
+++ b/Documentation/security/LSM.rst
@@ -5,7 +5,7 @@ Linux Security Module Development
 Based on https://lkml.org/lkml/2007/10/26/215,
 a new LSM is accepted into the kernel when its intent (a description of
 what it tries to protect against and in what cases one would expect to
-use it) has been appropriately documented in ``Documentation/security/LSM``.
+use it) has been appropriately documented in ``Documentation/security/LSM.rst``.
 This allows an LSM's code to be easily compared to its goals, and so
 that end users and distros can make a more informed decision about which
 LSMs suit their requirements.
diff --git a/Documentation/security/credentials.rst b/Documentation/security/credentials.rst
index 038a7e19eff9..66a2e24939d8 100644
--- a/Documentation/security/credentials.rst
+++ b/Documentation/security/credentials.rst
@@ -196,7 +196,7 @@ The Linux kernel supports the following types of credentials:
      When a process accesses a key, if not already present, it will normally be
      cached on one of these keyrings for future accesses to find.
 
-     For more information on using keys, see Documentation/security/keys.txt.
+     For more information on using keys, see ``Documentation/security/keys/*``.
 
  5. LSM
 
diff --git a/Documentation/security/keys/request-key.rst b/Documentation/security/keys/request-key.rst
index b2d16abaa9e9..21e27238cec6 100644
--- a/Documentation/security/keys/request-key.rst
+++ b/Documentation/security/keys/request-key.rst
@@ -3,7 +3,7 @@ Key Request Service
 ===================
 
 The key request service is part of the key retention service (refer to
-Documentation/security/core.rst).  This document explains more fully how
+Documentation/security/keys/core.rst).  This document explains more fully how
 the requesting algorithm works.
 
 The process starts by either the kernel requesting a service by calling
-- 
2.14.2

  parent reply	other threads:[~2017-10-10 17:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10 17:35 [PATCH 0/8] Documentation: fix invalid Documentation refs (1) Tom Saeger
2017-10-10 17:36 ` [PATCH 1/8] Documentation: fix driver-api doc refs Tom Saeger
2017-10-10 21:39   ` Rafael J. Wysocki
2017-10-10 17:36 ` [PATCH 2/8] Documentation: fix admin-guide " Tom Saeger
2017-10-10 21:40   ` Rafael J. Wysocki
2017-10-10 17:36 ` [PATCH 3/8] Documentation: fix input related " Tom Saeger
2017-10-10 18:08   ` Takashi Iwai
2017-10-10 17:36 ` Tom Saeger [this message]
2017-10-10 17:36 ` [PATCH 5/8] Documentation: fix media " Tom Saeger
2017-10-10 17:36 ` [PATCH 6/8] Documentation: fix sound " Tom Saeger
2017-10-10 18:09   ` Takashi Iwai
2017-10-10 17:36 ` [PATCH 7/8] Documentation: fix usb " Tom Saeger
2017-10-10 17:37 ` [PATCH 8/8] Documentation: fix networking " Tom Saeger
2017-10-12 17:24 ` [PATCH 0/8] Documentation: fix invalid Documentation refs (1) Jonathan Corbet
2017-10-12 19:01   ` Tom Saeger

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=cdf92bcf04d0c065308c8590fca1cdb7376fb373.1507653970.git.tom.saeger@oracle.com \
    --to=tom.saeger@oracle.com \
    --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

all inboxes | Powered by JetHome®