Change in coreboot[master]: security/tpm: Fix references to tpm_setup function

[Philipp Deppenwiese (Code Review)]

Philipp Deppenwiese has submitted this change and it was merged. ( https://review.coreboot.org/29349 )

Change subject: security/tpm: Fix references to tpm_setup function
......................................................................

security/tpm: Fix references to tpm_setup function

Change-Id: Ia97ddcd5471f8e5db50f57b67a766f08a08180b1
Signed-off-by: Jonathan Neuschäfer 
Reviewed-on: https://review.coreboot.org/29349
Tested-by: build bot (Jenkins) 
Reviewed-by: Philipp Deppenwiese 
---
M src/security/tpm/tspi/tspi.c
1 file changed, 3 insertions(+), 3 deletions(-)

Approvals:
  build bot (Jenkins): Verified
  Philipp Deppenwiese: Looks good to me, approved

diff --git a/src/security/tpm/tspi/tspi.c b/src/security/tpm/tspi/tspi.c
index d9cade9..0b6f9bc 100644
--- a/src/security/tpm/tspi/tspi.c
+++ b/src/security/tpm/tspi/tspi.c
@@ -103,10 +103,10 @@

/*
  * tpm_setup starts the TPM and establishes the root of trust for the
- * anti-rollback mechanism.  SetupTPM can fail for three reasons.  1 A bug. 2 a
- * TPM hardware failure. 3 An unexpected TPM state due to some attack.  In
+ * anti-rollback mechanism.  tpm_setup can fail for three reasons.  1 A bug.
+ * 2 a TPM hardware failure. 3 An unexpected TPM state due to some attack.  In
  * general we cannot easily distinguish the kind of failure, so our strategy is
- * to reboot in recovery mode in all cases.  The recovery mode calls SetupTPM
+ * to reboot in recovery mode in all cases.  The recovery mode calls tpm_setup
  * again, which executes (almost) the same sequence of operations.  There is a
  * good chance that, if recovery mode was entered because of a TPM failure, the
  * failure will repeat itself.  (In general this is impossible to guarantee