From: Jarkko Sakkinen <jarkko@kernel.org>
To: Sohaib Mohamed <sohaib.amhmd@gmail.com>
Cc: Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tpm/st33zp24: Fix typo in st33zp24.c
Date: Tue, 12 Oct 2021 18:20:34 +0300 [thread overview]
Message-ID: <500c72ecc99c127838dd4bded1e70fa48a1e97a3.camel@kernel.org> (raw)
In-Reply-To: <20211008052736.629562-1-sohaib.amhmd@gmail.com>
On Fri, 2021-10-08 at 07:27 +0200, Sohaib Mohamed wrote:
> Remove repeated world "device"
> "datas" -> "data"
>
> Signed-off-by: Sohaib Mohamed <sohaib.amhmd@gmail.com>
> ---
> drivers/char/tpm/st33zp24/st33zp24.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/char/tpm/st33zp24/st33zp24.c b/drivers/char/tpm/st33zp24/st33zp24.c
> index 4ec10ab5e576..f888624c1ae7 100644
> --- a/drivers/char/tpm/st33zp24/st33zp24.c
> +++ b/drivers/char/tpm/st33zp24/st33zp24.c
> @@ -62,7 +62,7 @@ enum tis_defaults {
>
> /*
> * clear_interruption clear the pending interrupt.
> - * @param: tpm_dev, the tpm device device.
> + * @param: tpm_dev, the tpm device.
> * @return: the interrupt status value.
> */
> static u8 clear_interruption(struct st33zp24_dev *tpm_dev)
> @@ -434,7 +434,7 @@ static int st33zp24_send(struct tpm_chip *chip, unsigned char *buf,
> /*
> * st33zp24_recv received TPM response through TPM phy.
> * @param: chip, the tpm_chip description as specified in driver/char/tpm/tpm.h.
> - * @param: buf, the buffer to store datas.
> + * @param: buf, the buffer to store data.
> * @param: count, the number of bytes to send.
> * @return: In case of success the number of bytes received.
> * In other case, a < 0 value describing the issue.
> --
> 2.25.1
>
So, these do not follow kdoc syntax, and they are only local functions,
i.e. it does not make sense to fix something that is already broken.
Having parameter descriptions for these is quite useless thing to
maintain so you could just remove parameter descriptions, and make
just a normal multi-line comment.
E.g.
/*
* Clear the pending input.
*/
static u8 clear_interruption(struct st33zp24_dev *tpm_dev)
For the 2nd the current description is barely even a proper sentence,
and it does not tell what the function does. Also for that you know
what it does already, since it is just implementing the callback.
So for that, just remove the comment altogether.
Please add to the next patch version:
Suggested-by: Jarkko Sakkinen <jarkko@kernel.org>
/Jarkko
prev parent reply other threads:[~2021-10-12 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 5:27 Sohaib Mohamed
2021-10-12 15:20 ` Jarkko Sakkinen [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=500c72ecc99c127838dd4bded1e70fa48a1e97a3.camel@kernel.org \
--to=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=sohaib.amhmd@gmail.com \
/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®