From: Jerome Pinot <ngc891@gmail.com>
To: Rui Saraiva <rmps@joel.ist.utl.pt>
Cc: lkml <linux-kernel@vger.kernel.org>,
Kylene Hall <kjhall@us.ibm.com>,
<tpmdd-devel@lists.sourceforge.net>
Subject: Re: [PATCH][2.6.16-rc1] TPM: tpm_bios needs securityfs (CONFIG_SECURITY)
Date: Wed, 18 Jan 2006 02:00:53 +0900 [thread overview]
Message-ID: <200601171700.k0HH0rAf000466@comet.localnet> (raw)
In-Reply-To: <Pine.LNX.4.64.0601171359120.25253@joel.ist.utl.pt>
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>
---
diff -Naur a/drivers/char/tpm/Kconfig b/drivers/char/tpm/Kconfig
--- a/drivers/char/tpm/Kconfig 2006-01-17 16:12:37.000000000 +0000
+++ b/drivers/char/tpm/Kconfig 2006-01-17 16:13:05.000000000 +0000
@@ -6,7 +6,7 @@
config TCG_TPM
tristate "TPM Hardware Support"
- depends on EXPERIMENTAL
+ depends on EXPERIMENTAL && SECURITY
---help---
If you have a TPM security chip in your system, which
implements the Trusted Computing Group's specification,
next prev parent reply other threads:[~2006-01-17 17:01 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 ` Jerome Pinot [this message]
2006-01-17 17:26 ` [PATCH][2.6.16-rc1] TPM: tpm_bios needs securityfs (CONFIG_SECURITY) Kylene Jo Hall
2006-01-22 7:38 ` Andrew Morton
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=200601171700.k0HH0rAf000466@comet.localnet \
--to=ngc891@gmail.com \
--cc=kjhall@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).