From: Josh Boyer <jwboyer@redhat.com>
To: Rob Landley <rob@landley.net>, Miklos Szeredi <mszeredi@suse.cz>,
akpm@linux-foundation.org
Cc: Serge Hallyn <serge.hallyn@canonical.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH RESEND] Documentation: kernel-parameters.txt remove capability.disable
Date: Tue, 18 Dec 2012 12:25:01 -0500 [thread overview]
Message-ID: <20121218172500.GC19265@hansolo.jdub.homelinux.org> (raw)
Remove the documentation for capability.disable. The code supporting this
parameter was removed with:
commit 5915eb53861c5776cfec33ca4fcc1fd20d66dd27
Author: Miklos Szeredi <mszeredi@suse.cz>
Date: Thu Jul 3 20:56:05 2008 +0200
security: remove dummy module
Acked-by: Serge Hallyn <serge.hallyn@canonical.com>
Signed-off-by: Josh Boyer <jwboyer@redhat.com>
---
Resend: I sent this back in June. It didn't stick: https://lkml.org/lkml/2012/6/25/538
Documentation/kernel-parameters.txt | 6 ------
1 file changed, 6 deletions(-)
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index ddd84d6..363e348 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -446,12 +446,6 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
possible to determine what the correct size should be.
This option provides an override for these situations.
- capability.disable=
- [SECURITY] Disable capabilities. This would normally
- be used only if an alternative security model is to be
- configured. Potentially dangerous and should only be
- used if you are entirely sure of the consequences.
-
ccw_timeout_log [S390]
See Documentation/s390/CommonIO for details.
--
1.8.0.1
next reply other threads:[~2012-12-18 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 17:25 Josh Boyer [this message]
2012-12-20 8:12 ` [PATCH RESEND] Documentation: kernel-parameters.txt remove capability.disable Rob Landley
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=20121218172500.GC19265@hansolo.jdub.homelinux.org \
--to=jwboyer@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@suse.cz \
--cc=rob@landley.net \
--cc=serge.hallyn@canonical.com \
/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