From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Justin M. Forbes" <jforbes@fedoraproject.org>,
"Peter Huewe" <peterhuewe@gmx.de>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Ivan Orlov" <ivan.orlov0322@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
<linux-integrity@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <jmforbes@linuxtx.org>
Subject: Re: [PATCH] Fix typo in tpmrm class definition
Date: Tue, 12 Sep 2023 00:48:41 +0300 [thread overview]
Message-ID: <CVGF3OAVF2W6.3V99S2XAHPTHC@suppilovahvero> (raw)
In-Reply-To: <20230908140629.2930150-1-jforbes@fedoraproject.org>
On Fri Sep 8, 2023 at 5:06 PM EEST, Justin M. Forbes wrote:
> Commit d2e8071bed0be ("tpm: make all 'class' structures const")
> unfortunately had a typo for the name on tpmrm.
>
> Fixes: d2e8071bed0b ("tpm: make all 'class' structures const")
> Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
> ---
> drivers/char/tpm/tpm-chip.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/char/tpm/tpm-chip.c b/drivers/char/tpm/tpm-chip.c
> index 23f6f2eda84c..42b1062e33cd 100644
> --- a/drivers/char/tpm/tpm-chip.c
> +++ b/drivers/char/tpm/tpm-chip.c
> @@ -33,7 +33,7 @@ const struct class tpm_class = {
> .shutdown_pre = tpm_class_shutdown,
> };
> const struct class tpmrm_class = {
> - .name = "tmprm",
> + .name = "tpmrm",
> };
> dev_t tpm_devt;
>
> --
> 2.41.0
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
Thanks, I'll queue this up for rc2.
BR, Jarkko
next prev parent reply other threads:[~2023-09-12 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 14:06 [PATCH] Fix typo in tpmrm class definition Justin M. Forbes
2023-09-09 19:58 ` Ivan Orlov
2023-09-11 21:48 ` Jarkko Sakkinen [this message]
2023-09-11 21:53 ` Jarkko Sakkinen
2023-09-11 22:34 ` Justin Forbes
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=CVGF3OAVF2W6.3V99S2XAHPTHC@suppilovahvero \
--to=jarkko@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=ivan.orlov0322@gmail.com \
--cc=jforbes@fedoraproject.org \
--cc=jgg@ziepe.ca \
--cc=jmforbes@linuxtx.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.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