mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: linux-security-module@vger.kernel.org,
	James Morris <jmorris@namei.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Randy Dunlap <rdunlap@xenotime.net>,
	Arnaud Lacombe <lacombar@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	David Safford <safford@watson.ibm.com>,
	Mimi Zohar <zohar@us.ibm.com>
Subject: Re: [PATCH v1 1/2] encrypted-keys: remove trusted-keys dependency
Date: Mon, 29 Aug 2011 11:46:26 -0400	[thread overview]
Message-ID: <1314632786.3534.38.camel@localhost.localdomain> (raw)
In-Reply-To: <1314629812.29761.21.camel@sasha>

On Mon, 2011-08-29 at 17:56 +0300, Sasha Levin wrote:
> On Mon, 2011-08-29 at 10:48 -0400, Mimi Zohar wrote:
> > Encrypted keys are decrypted/encrypted using either a trusted-key or,
> > for those systems without a TPM, a user-defined key.  This patch
> > removes the trusted-keys and TCG_TPM dependencies.
> > 
> > Changelog v1:
> > - Fixed encrypted-keys move from security/keys to security/keys/encrypted-keys
> > - Removed trailing blank line
> > 
> > Signed-off-by: Mimi Zohar <zohar@us.ibm.com>
> > ---
> 
> Please look into using 'git mv' and the '--find-renames' option of git
> format-patch.
> 
> You just want to mark the files as moved, without ruining the entire
> history of the old files.
> 

Thanks for the tip. 'git blame' shows multiple commits, but perhaps if
encrypted-keys had a longer history some of it would have been lost.
I'll keep your suggestion in mind in the future.

thanks,

Mimi


      reply	other threads:[~2011-08-29 15:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-29 14:48 Mimi Zohar
2011-08-29 14:48 ` [PATCH v1 2/2] evm: remove TCG_TPM dependency Mimi Zohar
2011-08-29 14:56 ` [PATCH v1 1/2] encrypted-keys: remove trusted-keys dependency Sasha Levin
2011-08-29 15:46   ` Mimi Zohar [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=1314632786.3534.38.camel@localhost.localdomain \
    --to=zohar@linux.vnet.ibm.com \
    --cc=jmorris@namei.org \
    --cc=lacombar@gmail.com \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=safford@watson.ibm.com \
    --cc=sfr@canb.auug.org.au \
    --cc=zohar@us.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
all inboxes | Powered by JetHome®