public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Serge Hallyn <serge.hallyn@canonical.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: James Morris <james.l.morris@oracle.com>,
	linux-security-module@vger.kernel.org,
	Casey Schaufler <casey@schaufler-ca.com>,
	linux-kernel@vger.kernel.org, Eric Paris <eparis@redhat.com>,
	"Andrew G. Morgan" <morgan@kernel.org>,
	mtk.manpages@gmail.com
Subject: Re: [PATCH] Document how capability bits work
Date: Fri, 7 Dec 2012 13:21:38 -0600	[thread overview]
Message-ID: <20121207192138.GA22308@sergelap> (raw)
In-Reply-To: <3c3146b8bea5d8590ebc40ca1d22a562a5172873.1354904275.git.luto@amacapital.net>

Quoting Andy Lutomirski (luto@amacapital.net):
> Signed-off-by: Andy Lutomirski <luto@amacapital.net>
> ---
>  Documentation/security/capabilities.txt | 161 ++++++++++++++++++++++++++++++++
>  1 file changed, 161 insertions(+)
>  create mode 100644 Documentation/security/capabilities.txt

TBH, I think a pointer to the capabilities.7 man page would be better.
(plus, if you feel they are needed, updates to the man page)

(I'll refrain from detailed review of the contents until this is
discussed.)

-serge

  reply	other threads:[~2012-12-07 19:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07 18:20 [PATCH] Document how capability bits work Andy Lutomirski
2012-12-07 19:21 ` Serge Hallyn [this message]
2012-12-07 19:32   ` Andy Lutomirski
2012-12-08  1:10     ` Rob Landley
2012-12-08  1:27       ` Andy Lutomirski
2012-12-08  9:51         ` Rob Landley
2012-12-10  5:57           ` Serge Hallyn
2012-12-09  9:54         ` Michael Kerrisk (man-pages)

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=20121207192138.GA22308@sergelap \
    --to=serge.hallyn@canonical.com \
    --cc=casey@schaufler-ca.com \
    --cc=eparis@redhat.com \
    --cc=james.l.morris@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=morgan@kernel.org \
    --cc=mtk.manpages@gmail.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