mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org, safford@watson.ibm.com,
	serue@linux.vnet.ibm.com, sailer@watson.ibm.com,
	zohar@us.ibm.com, Stephen Smalley <sds@tycho.nsa.gov>,
	CaseySchaufler <casey@schaufler-ca.com>
Subject: Re: [RFC][Patch 1/4]integrity: TPM internel kernel interface
Date: Thu, 22 May 2008 14:39:53 -0400	[thread overview]
Message-ID: <1211481593.4867.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20080522150516.GB25721@elf.ucw.cz>


On Thu, 2008-05-22 at 17:05 +0200, Pavel Machek wrote:
> On Wed 2008-05-21 11:54:16, Mimi Zohar wrote:
> > This is a request for comments for a redesign of the integrity patches.
> > This patchset contains 4 patches.
> > 	Patch 1/4 integrity: TPM internal kernel interface
> > 	Patch 2/4 integrity: special fs magic
> > 	Patch 3/4 integrity: Linux Integrity Module(LIM)
> > 	Patch 4/4 integrity: IMA as an integrity service provider
> >  
> > Resubmitting integrity-tpm-internal-kernel-interface.patch, which
> > was previously Signed-off-by Kylene Hall.
> > 
> > Adds the following support: 
> > - internal kernel interface to transmit TPM commands
> > - reading a pcr value
> > - extending a pcr value
> > - lookup the tpm_chip for given chip number and type
> > 
> > Signed-off-by: Mimi Zohar <zohar@us.ibm.com>
> 
> >  /*
> > - * Returns max number of jiffies to wait
> > + * tpm_calc_ordinal_duration - returns max number of jiffies to wait
> >   */
> > -unsigned long tpm_calc_ordinal_duration(struct tpm_chip *chip,
> > -					   u32 ordinal)
> > +unsigned long tpm_calc_ordinal_duration(struct tpm_chip *chip, u32 ordinal)
> 
> Please don't mix real changes and cleanups... and lots of your changes
> are just cleanups.
> 
> > @@ -544,7 +549,7 @@ duration:
> >  	data[TPM_CAP_SUBCAP_IDX] = TPM_CAP_PROP_TIS_DURATION;
> >  
> >  	rc = transmit_cmd(chip, data, sizeof(data),
> > -			"attempting to determine the durations");
> > +			  "attempting to determine the durations");
> >  	if (rc)
> >  		return;
> >
> 
> ...like this.
> 									Pavel

Ok.  Will separate the changes, from the scripts/Lindent cleanups. 

Mimi


      reply	other threads:[~2008-05-22 18:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21 15:54 Mimi Zohar
2008-05-22 15:05 ` Pavel Machek
2008-05-22 18:39   ` 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=1211481593.4867.9.camel@localhost.localdomain \
    --to=zohar@linux.vnet.ibm.com \
    --cc=casey@schaufler-ca.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=safford@watson.ibm.com \
    --cc=sailer@watson.ibm.com \
    --cc=sds@tycho.nsa.gov \
    --cc=serue@linux.vnet.ibm.com \
    --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®