[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190403181936.GC17006@linux.intel.com>
Date: Wed, 3 Apr 2019 21:19:36 +0300
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: Sasha Levin <sashal@...nel.org>, robh+dt@...nel.org,
mark.rutland@....com, peterhuewe@....de, jgg@...pe.ca,
Microsoft Linux Kernel List <linux-kernel@...rosoft.com>,
"Bryan Kelly (CSI)" <bryankel@...rosoft.com>,
Thirupathaiah Annapureddy <thiruan@...rosoft.com>,
Sudhakar Evuri <suredd@...rosoft.com>, arnd@...db.de,
gregkh@...uxfoundation.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-integrity@...r.kernel.org
Subject: Re: [PATCH 2/2] ftpm: firmware TPM running in TEE
On Tue, Apr 02, 2019 at 01:56:43PM -0700, Stephen Hemminger wrote:
> On Tue, 2 Apr 2019 12:33:16 -0700
> "Sasha Levin" <sashal@...nel.org> wrote:
>
> > +/*
> > + * ftpm_tee_tpm_op_recv retrieve fTPM response.
> > + * @param: chip, the tpm_chip description as specified in
> > driver/char/tpm/tpm.h.
> > + * @param: buf, the buffer to store data.
> > + * @param: count, the number of bytes to read.
> > + * @return: In case of success the number of bytes received.
> > + * In other case, a < 0 value describing the issue.
> > + */
>
> You are using a docbook style comment but it doesn't start with
> docbook prefix.
>
> /**
> * ftpm_tee_tpm_op_recv retrieve fTPM response.
> *
> * @param: chip, the tpm_chip description as specified in driver/char/tpm/tpm.h.
> * @param: buf, the buffer to store data.
> * @param: count, the number of bytes to read.
> * @return: In case of success the number of bytes received.
> * In other case, a < 0 value describing the issue.
> */
This is different commenting style that we use on anything else
under drivers/char/tpm.
/Jarkko
Powered by blists - more mailing lists