linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Dmitry Kasatkin <dmitry.kasatkin@intel.com>,
	Mimi Zohar <zohar@linux.vnet.ibm.com>
Subject: Re: [GIT] Security subsystem updates for 3.3
Date: Wed, 11 Jan 2012 18:35:50 +1100 (EST)	[thread overview]
Message-ID: <alpine.LRH.2.00.1201111834570.2966@tundra.namei.org> (raw)
In-Reply-To: <CA+55aFwD2-bhd32L1SsjPQrpwOBhBdxTUaOj=oXN24vPwc+Wsg@mail.gmail.com>

On Tue, 10 Jan 2012, Linus Torvalds wrote:

> Hmm. The CONFIG_MPI/DIGSIG thing really should go away as a question,
> I think. I'd expect modules that need it to select it, there's no
> point in asking a user "do you want this enabled" afaik.

Ok.

> 
> And "DIGSIG" is really a horrible config name. Did somebody run out of
> letters suddenly? Is there some global letter shortage that I haven't
> been told of and that we should do something about?

Any objections to DIGITAL_SIGNATURE_API ?

> But I pulled it. Please do fix it up, though.

Thanks, will do.


- James
-- 
James Morris
<jmorris@namei.org>

  reply	other threads:[~2012-01-11  7:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09  2:22 [GIT] Security subsystem updates for 3.3 James Morris
2012-01-11  5:58 ` Linus Torvalds
2012-01-11  7:35   ` James Morris [this message]
2012-01-11  8:11     ` Sam Ravnborg
2012-01-11 14:51     ` Linus Torvalds
2012-01-11 15:15       ` Kasatkin, Dmitry
2012-01-11 16:12         ` Linus Torvalds
2012-01-15 10:38         ` Pavel Machek

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=alpine.LRH.2.00.1201111834570.2966@tundra.namei.org \
    --to=jmorris@namei.org \
    --cc=dmitry.kasatkin@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=zohar@linux.vnet.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;
as well as URLs for NNTP newsgroup(s).