From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Serge Hallyn <serge.hallyn@canonical•com>
Cc: James Morris <jmorris@namei•org>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Eric Paris <eparis@redhat•com>
Subject: Re: linux-next: manual merge of the security-testing tree with Linus' tree
Date: Tue, 17 May 2011 00:52:06 +1000 [thread overview]
Message-ID: <20110517005206.4158b74a.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20110516141359.GA9430@mail.hallyn.com>
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
Hi Serge,
On Mon, 16 May 2011 09:13:59 -0500 Serge Hallyn <serge.hallyn@canonical•com> wrote:
>
> looking at commit ffa8e59df047, it also adds
>
> +extern const kernel_cap_t __cap_full_set;
>
> under __cap_empty_set. My trees are a bit screwed up so I'm not sure if
> that gets later removed, but I just wanted to make sure you didn't
> accidentally drop that.
Yeah, it got removed in the next commit (5163b583a036 "capabilities:
delete unused cap_set_full"), sorry for not mentioning that.
> Otherwise looks good,
Thanks.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-05-16 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 3:02 linux-next: manual merge of the security-testing tree with Linus' tree Stephen Rothwell
2011-05-16 14:13 ` Serge Hallyn
2011-05-16 14:52 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-06 2:30 Stephen Rothwell
2010-05-06 10:49 ` David Howells
2010-05-06 23:10 ` James Morris
2010-05-06 23:24 ` Justin P. Mattock
2009-05-22 5:29 Stephen Rothwell
2009-05-22 5:35 ` Al Viro
2009-05-22 9:04 ` James Morris
2009-02-06 7:23 Stephen Rothwell
2009-02-06 8:12 ` James Morris
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=20110517005206.4158b74a.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=eparis@redhat$(echo .)com \
--cc=jmorris@namei$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=serge.hallyn@canonical$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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