public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: sds@tycho.nsa.gov, serue@us.ibm.com,
	linux-security-module@vger.kernel.org, morgan@kernel.org,
	chrisw@sous-sol.org, linux-kernel@vger.kernel.org,
	kaigai@kaigai.gr.jp, casey@schaufler-ca.com
Subject: Re: [RFC] [PATCH 2/2] capabilities: implement 64-bit capabilities
Date: Wed, 17 Oct 2007 18:00:02 -0700	[thread overview]
Message-ID: <20071017180002.33fe4986.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071016214159.GB13294@sergelap.austin.ibm.com>

On Tue, 16 Oct 2007 16:41:59 -0500
"Serge E. Hallyn" <serue@us.ibm.com> wrote:

> To properly test this the libcap code will need to be updated first,
> which I'm looking at now...

This seems fairly significant.  I asusme that this patch won't break
presently-deployed libcap?

  reply	other threads:[~2007-10-18  1:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16  2:27 [PATCH 1/2 -mm] capabilities: clean up file capability reading Serge E. Hallyn
2007-10-16  2:31 ` [RFC] [PATCH 2/2] capabilities: implement 64-bit capabilities Serge E. Hallyn
2007-10-16 14:18   ` Stephen Smalley
2007-10-16 18:48     ` Serge E. Hallyn
2007-10-16 21:41     ` Serge E. Hallyn
2007-10-18  1:00       ` Andrew Morton [this message]
2007-10-18  2:59         ` Serge E. Hallyn
2007-10-18  3:13           ` Casey Schaufler
2007-10-18  3:20           ` Andrew Morton
2007-10-18  5:21           ` Chris Wright
2007-10-18 12:50             ` Serge E. Hallyn
2007-10-18 15:27               ` Andrew Morgan
2007-10-18 15:30                 ` Serge E. Hallyn
2007-10-18 15:30               ` Chris Wright

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=20071017180002.33fe4986.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=casey@schaufler-ca.com \
    --cc=chrisw@sous-sol.org \
    --cc=kaigai@kaigai.gr.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=morgan@kernel.org \
    --cc=sds@tycho.nsa.gov \
    --cc=serue@us.ibm.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