From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: keyrings@vger.kernel.org
Subject: Re: [PATCH RESEND] KEYS: remove CONFIG_KEYS_COMPAT
Date: Thu, 12 Dec 2019 21:44:06 +0000 [thread overview]
Message-ID: <20191212214330.GA31054@linux.intel.com> (raw)
In-Reply-To: <20180105191947.91775-1-ebiggers3@gmail.com>
On Mon, Oct 14, 2019 at 10:53:54PM +0300, Jarkko Sakkinen wrote:
> On Wed, Oct 09, 2019 at 04:04:43PM -0700, Eric Biggers wrote:
> > From: Eric Biggers <ebiggers@google.com>
> >
> > KEYS_COMPAT now always takes the value of COMPAT && KEYS. But the
> > security/keys/ directory is only compiled if KEYS is enabled, so in
> > practice KEYS_COMPAT is the same as COMPAT. Therefore, remove the
> > unnecessary KEYS_COMPAT and just use COMPAT directly.
> >
> > (Also remove an outdated comment from compat.c.)
> >
> > Reviewed-by: James Morris <jamorris@linux.microsoft.com>
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
>
> Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> Tested-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
>
> (aka compiling with the different combinations).
I applied this to git://git.infradead.org/users/jjs/linux-tpmdd.git
/Jarkko
prev parent reply other threads:[~2019-12-12 21:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 19:19 [PATCH RESEND] KEYS: remove CONFIG_KEYS_COMPAT Eric Biggers
2018-02-20 19:41 ` Eric Biggers
2018-05-08 18:06 ` Eric Biggers
2018-11-15 0:52 ` Eric Biggers
2019-01-10 20:28 ` Eric Biggers
2019-02-07 23:35 ` Eric Biggers
2019-03-18 17:28 ` Eric Biggers
2019-05-29 21:02 ` Eric Biggers
2019-05-29 21:49 ` James Morris
2019-08-22 15:36 ` Eric Biggers
2019-10-09 23:04 ` Eric Biggers
2019-10-14 19:53 ` Jarkko Sakkinen
2019-11-11 18:20 ` Eric Biggers
2019-11-12 20:08 ` Jarkko Sakkinen
2019-12-09 20:18 ` Eric Biggers
2019-12-11 11:03 ` Jarkko Sakkinen
2019-12-12 21:44 ` Jarkko Sakkinen [this message]
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=20191212214330.GA31054@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=keyrings@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox