From: Eric Biggers <ebiggers3@gmail.com>
To: linux-security-module@vger.kernel.org
Subject: Re: [PATCH] KEYS: remove CONFIG_KEYS_COMPAT
Date: Wed, 16 Aug 2017 02:52:44 +0000 [thread overview]
Message-ID: <20170816025244.GA1417@zzz.localdomain> (raw)
In-Reply-To: <7704.1498555674@warthog.procyon.org.uk>
On Tue, Jun 27, 2017 at 10:27:54AM +0100, David Howells wrote:
> Eric Biggers <ebiggers3@gmail.com> wrote:
>
> > diff --git a/security/keys/Kconfig b/security/keys/Kconfig
> > index a7a23b5541f8..f5d96996baa6 100644
> > --- a/security/keys/Kconfig
> > +++ b/security/keys/Kconfig
> > @@ -20,10 +20,6 @@ config KEYS
> >
> > If you are unsure as to whether this is required, answer N.
> >
> > -config KEYS_COMPAT
> > - def_bool y
> > - depends on COMPAT && KEYS
> > -
> > config PERSISTENT_KEYRINGS
> > bool "Enable register of persistent per-UID keyrings"
> > depends on KEYS
>
> Hmmm... This is in linus/master, but not in security/next. I'll hold your
> patch till later in the merge window or just after -rc1.
>
> David
Hi David, are you still planning to apply this patch?
Eric
WARNING: multiple messages have this Message-ID (diff)
From: ebiggers3@gmail.com (Eric Biggers)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] KEYS: remove CONFIG_KEYS_COMPAT
Date: Tue, 15 Aug 2017 19:52:44 -0700 [thread overview]
Message-ID: <20170816025244.GA1417@zzz.localdomain> (raw)
In-Reply-To: <7704.1498555674@warthog.procyon.org.uk>
On Tue, Jun 27, 2017 at 10:27:54AM +0100, David Howells wrote:
> Eric Biggers <ebiggers3@gmail.com> wrote:
>
> > diff --git a/security/keys/Kconfig b/security/keys/Kconfig
> > index a7a23b5541f8..f5d96996baa6 100644
> > --- a/security/keys/Kconfig
> > +++ b/security/keys/Kconfig
> > @@ -20,10 +20,6 @@ config KEYS
> >
> > If you are unsure as to whether this is required, answer N.
> >
> > -config KEYS_COMPAT
> > - def_bool y
> > - depends on COMPAT && KEYS
> > -
> > config PERSISTENT_KEYRINGS
> > bool "Enable register of persistent per-UID keyrings"
> > depends on KEYS
>
> Hmmm... This is in linus/master, but not in security/next. I'll hold your
> patch till later in the merge window or just after -rc1.
>
> David
Hi David, are you still planning to apply this patch?
Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-08-16 2:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 6:09 [PATCH] KEYS: remove CONFIG_KEYS_COMPAT Eric Biggers
2017-06-13 6:09 ` Eric Biggers
2017-06-27 9:27 ` David Howells
2017-06-27 9:27 ` David Howells
2017-08-16 2:52 ` Eric Biggers [this message]
2017-08-16 2:52 ` Eric Biggers
2017-10-09 20:25 ` Eric Biggers
2017-10-09 20:25 ` Eric Biggers
2017-11-13 22:56 ` Eric Biggers
2017-11-13 22:56 ` Eric Biggers
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=20170816025244.GA1417@zzz.localdomain \
--to=ebiggers3@gmail.com \
--cc=linux-security-module@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.