From: "Limonciello, Mario" <Mario.Limonciello@amd.com>
To: Yunseong Kim <ysk@kzalloc.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
"Allen, John" <John.Allen@amd.com>,
"David S. Miller" <davem@davemloft.net>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] crypto: ccp: Fix typo in psp_populate_hsti function name
Date: Tue, 19 Aug 2025 19:54:39 +0000 [thread overview]
Message-ID: <d0764649-5309-494a-b173-bc04aca2a054@amd.com> (raw)
In-Reply-To: <20250816143028.1111603-2-ysk@kzalloc.com>
On 8/16/25 9:30 AM, Yunseong Kim wrote:
> The function "psp_poulate_hsti" was misspelled. This patch corrects
> the typo to "psp_populate_hsti" in both the function definition and
> its call site within psp_init_hsti().
>
> Signed-off-by: Yunseong Kim <ysk@kzalloc.com>
Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>> ---
> drivers/crypto/ccp/hsti.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/crypto/ccp/hsti.c b/drivers/crypto/ccp/hsti.c
> index 1b39a4fb55c0..2e23ff7f3b18 100644
> --- a/drivers/crypto/ccp/hsti.c
> +++ b/drivers/crypto/ccp/hsti.c
> @@ -74,7 +74,7 @@ struct attribute_group psp_security_attr_group = {
> .is_visible = psp_security_is_visible,
> };
>
> -static int psp_poulate_hsti(struct psp_device *psp)
> +static int psp_populate_hsti(struct psp_device *psp)
> {
> struct hsti_request *req;
> int ret;
> @@ -114,7 +114,7 @@ int psp_init_hsti(struct psp_device *psp)
> int ret;
>
> if (PSP_FEATURE(psp, HSTI)) {
> - ret = psp_poulate_hsti(psp);
> + ret = psp_populate_hsti(psp);
> if (ret)
> return ret;
> }
next prev parent reply other threads:[~2025-08-19 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 14:30 [PATCH] crypto: ccp: Fix typo in psp_populate_hsti function name Yunseong Kim
2025-08-19 19:54 ` Limonciello, Mario [this message]
2025-08-22 9:34 ` Herbert Xu
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=d0764649-5309-494a-b173-bc04aca2a054@amd.com \
--to=mario.limonciello@amd.com \
--cc=John.Allen@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ysk@kzalloc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.