From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752499Ab2AOKiJ (ORCPT ); Sun, 15 Jan 2012 05:38:09 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:55273 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751935Ab2AOKiH (ORCPT ); Sun, 15 Jan 2012 05:38:07 -0500 Date: Sun, 15 Jan 2012 11:38:04 +0100 From: Pavel Machek To: "Kasatkin, Dmitry" Cc: Linus Torvalds , James Morris , linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, Mimi Zohar Subject: Re: [GIT] Security subsystem updates for 3.3 Message-ID: <20120115103804.GB6698@atrey.karlin.mff.cuni.cz> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On Wed, Jan 11, 2012 at 4:51 PM, Linus Torvalds > wrote: > > On Tue, Jan 10, 2012 at 11:35 PM, James Morris wrote: > >>> 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 ? > > > > Sounds much better. Slightly more typing, but CONFIG_DIGSIG really > > didn't tell me anything and sounded like some odd new device to me. > > > >                          Linus > > Would just DIGITAL_SIGNATURE be enough? Actually, "CONFIG_SIGNATURE" should be enough. -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html