From: Pranith Kumar <bobby.prani@gmail.com>
To: trivial@rustcorp.com.au,
"GitAuthor: Pranith Kumar" <bobby.prani@gmail.com>,
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH 3/6] update reference, kerneltrap.org no longer works
Date: Mon, 9 Jun 2014 11:51:25 -0400 [thread overview]
Message-ID: <1402329088-4802-3-git-send-email-bobby.prani@gmail.com> (raw)
In-Reply-To: <1402329088-4802-1-git-send-email-bobby.prani@gmail.com>
kerneltrap.org no longer works, update to a working reference
Signed-off-by: Pranith Kumar <bobby.prani@gmail.com>
---
Documentation/security/LSM.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/security/LSM.txt b/Documentation/security/LSM.txt
index c335a76..3db7e67 100644
--- a/Documentation/security/LSM.txt
+++ b/Documentation/security/LSM.txt
@@ -22,7 +22,7 @@ system, building their checks on top of the defined capability hooks.
For more details on capabilities, see capabilities(7) in the Linux
man-pages project.
-Based on http://kerneltrap.org/Linux/Documenting_Security_Module_Intent,
+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/.
--
1.9.1
next prev parent reply other threads:[~2014-06-09 15:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 15:51 [PATCH 1/6] update reference, kerneltrap.org no longer works Pranith Kumar
2014-06-09 15:51 ` [PATCH 2/6] remove dead link, " Pranith Kumar
2014-06-09 15:51 ` Pranith Kumar [this message]
2014-06-09 15:51 ` [PATCH 4/6] update reference, " Pranith Kumar
2014-06-09 15:51 ` [PATCH 5/6] " Pranith Kumar
2014-06-09 15:51 ` [PATCH 6/6] remove dead link, " Pranith Kumar
2014-06-09 16:08 ` [PATCH 1/6] update reference, " Paul E. McKenney
-- strict thread matches above, loose matches on Subject: below --
2014-06-09 15:55 Pranith Kumar
2014-06-09 15:55 ` [PATCH 3/6] " Pranith Kumar
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=1402329088-4802-3-git-send-email-bobby.prani@gmail.com \
--to=bobby.prani@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@rustcorp.com.au \
/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