mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Kylene Jo Hall <kjhall@us.ibm.com>
Cc: ngc891@gmail.com, rmps@joel.ist.utl.pt,
	linux-kernel@vger.kernel.org, tpmdd-devel@lists.sourceforge.net
Subject: Re: [PATCH][2.6.16-rc1] TPM: tpm_bios needs securityfs (CONFIG_SECURITY)
Date: Sat, 21 Jan 2006 23:38:39 -0800	[thread overview]
Message-ID: <20060121233839.2aa99018.akpm@osdl.org> (raw)
In-Reply-To: <1137518808.4873.108.camel@localhost.localdomain>

Kylene Jo Hall <kjhall@us.ibm.com> wrote:
>
> Ack'ed-by: Kylene Hall <kjhall@us.ibm.com>
> 
> On Wed, 2006-01-18 at 02:00 +0900, Jerome Pinot wrote:
> > Hi,
> >  
> >  >It seems that "TPM Hardware Support" (CONFIG_TCG_TPM) depends on
> >  >"Enable different security models" (CONFIG_SECURITY).
> >  
> >  This does the trick but your patch formatting is broken. This one
> >  applies cleanly against 2.6.16-rc1.
> >  
> >  from: Rui Saraiva
> >  
> >  tpm_bios (CONFIG_TCG_TPM) depends on securityfs (CONFIG_SECURITY).
> >  
> >  Signed-off-by: Rui Saraiva <rmps@mail.pt>
> >  Signed-off-by: Jerome Pinot <ngc891@gmail.com>

No, this patch shouldn't be needed once we have the suitable security stubs
in place.

See
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc1/2.6.16-rc1-mm2/broken-out/tpm_bios-needs-more-securityfs_-functions.patch
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc1/2.6.16-rc1-mm2/broken-out/tpm_bios-securityfs-error-checking-fix.patch


      reply	other threads:[~2006-01-22  7:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 14:02 [PATCH 2.6.15+]: Trusted Platform depends on Security models Rui Saraiva
2006-01-17 17:00 ` [PATCH][2.6.16-rc1] TPM: tpm_bios needs securityfs (CONFIG_SECURITY) Jerome Pinot
2006-01-17 17:26   ` Kylene Jo Hall
2006-01-22  7:38     ` Andrew Morton [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=20060121233839.2aa99018.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=kjhall@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ngc891@gmail.com \
    --cc=rmps@joel.ist.utl.pt \
    --cc=tpmdd-devel@lists.sourceforge.net \
    /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®