From: Philipp Matthias Hahn <pmhahn@titan.lahn.de>
To: Marcel Selhorst <selhorst@crypto.rub.de>
Cc: linux-kernel@vger.kernel.org, kjhall@us.ibm.com, adobriyan@gmail.com
Subject: Re: [PATCH] tpm: Support for new chip type
Date: Fri, 8 Jul 2005 08:54:43 +0200 [thread overview]
Message-ID: <20050708065443.GA28565@titan.lahn.de> (raw)
In-Reply-To: <42CDAFBA.5080005@crypto.rub.de>
Hello!
On Fri, Jul 08, 2005 at 12:42:02AM +0200, Marcel Selhorst wrote:
> +++ linux/drivers/char/tpm/tpm_infineon.c 2005-07-07 14:56:27.000000000 +0000
...
> + * Specifications at www.trustedcomputinggroup.org
Blanks at end of line
> +/* Infineon specific delay definitions */
> +enum infineon_tpm_delay {
> + TPM_MAX_WTX_PACKAGES = 50, /* maximum number of WTX-packages */
> + TPM_WTX_MSLEEP_TIME = 20, /* msleep-Time for WTX-packages */
> + TPM_MSLEEP_TIME = 3, /* msleep-Time --> Interval to check status register */
> + TPM_MAX_TRIES = 5000 /* gives number of max. msleep()-calls before
> + throwing timeout */
> +};
These look like unrelated constants, perhaps #define would be nicer?
> +static int wait(struct tpm_chip *chip, int wait_for_bit)
> +{
> +
blank line
> +}
> +static void tpm_inf_cancel(struct tpm_chip *chip)
missing blank line
> +static int __init tpm_inf_probe(struct pci_dev *pci_dev,
> + const struct pci_device_id *pci_id)
> +{
> +
blank lines
> + return 0;
> +
> + } else {
BYtE
Philipp
--
/ / (_)__ __ ____ __ Philipp Hahn
/ /__/ / _ \/ // /\ \/ /
/____/_/_//_/\_,_/ /_/\_\ pmhahn@titan.lahn.de
next prev parent reply other threads:[~2005-07-08 6:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 22:42 [PATCH] tpm: Support for new chip type Marcel Selhorst
2005-07-08 6:54 ` Philipp Matthias Hahn [this message]
2005-07-08 7:16 ` Alexey Dobriyan
2005-07-09 19:19 ` Pavel Machek
2005-07-10 12:35 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
2005-07-05 12:49 Marcel Selhorst
2005-07-05 15:03 ` Alexey Dobriyan
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=20050708065443.GA28565@titan.lahn.de \
--to=pmhahn@titan.lahn.de \
--cc=adobriyan@gmail.com \
--cc=kjhall@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=selhorst@crypto.rub.de \
/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