From: Maxime MERE <maxime.mere@foss.st.com>
To: Colin Ian King <colin.i.king@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
<linux-crypto@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>
Cc: <kernel-janitors@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next] crypto: stm32: Fix spelling mistake "STMicrolectronics" -> "STMicroelectronics"
Date: Thu, 24 Jul 2025 14:07:19 +0200 [thread overview]
Message-ID: <7ef4ce0e-8690-43ab-90c4-84cebb4e58e7@foss.st.com> (raw)
In-Reply-To: <20250724105754.140400-1-colin.i.king@gmail.com>
Hi, thanks for the typo fix.
Acked-by: Maxime Méré <maxime.mere@foss.st.com>
On 7/24/25 12:57, Colin Ian King wrote:
> There is a spelling mistake in the module description text. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> drivers/crypto/stm32/stm32-cryp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/stm32/stm32-cryp.c b/drivers/crypto/stm32/stm32-cryp.c
> index a89b4c5d62a0..5e82e8a1f71a 100644
> --- a/drivers/crypto/stm32/stm32-cryp.c
> +++ b/drivers/crypto/stm32/stm32-cryp.c
> @@ -2781,5 +2781,5 @@ static struct platform_driver stm32_cryp_driver = {
> module_platform_driver(stm32_cryp_driver);
>
> MODULE_AUTHOR("Fabien Dessenne <fabien.dessenne@st.com>");
> -MODULE_DESCRIPTION("STMicrolectronics STM32 CRYP hardware driver");
> +MODULE_DESCRIPTION("STMicroelectronics STM32 CRYP hardware driver");
> MODULE_LICENSE("GPL");
next prev parent reply other threads:[~2025-07-24 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 10:57 [PATCH][next] crypto: stm32: Fix spelling mistake "STMicrolectronics" -> "STMicroelectronics" Colin Ian King
2025-07-24 12:07 ` Maxime MERE [this message]
2025-08-16 9:30 ` 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=7ef4ce0e-8690-43ab-90c4-84cebb4e58e7@foss.st.com \
--to=maxime.mere@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=colin.i.king@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@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;
as well as URLs for NNTP newsgroup(s).