lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6be1c1c6-8d8a-49e3-bb14-dc8fcbfc2c50@molgen.mpg.de>
Date: Thu, 3 Jul 2025 16:35:32 +0200
From: Paul Menzel <pmenzel@...gen.mpg.de>
To: Bastien Nocera <hadess@...ess.net>
Cc: trivial@...nel.org, Marcel Holtmann <marcel@...tmann.org>,
 Luiz Augusto von Dentz <luiz.dentz@...il.com>,
 Sean Wang <sean.wang@...iatek.com>, Matthias Brugger
 <matthias.bgg@...il.com>,
 AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
 Sven Peter <sven@...nel.org>, Janne Grunau <j@...nau.net>,
 Alyssa Rosenzweig <alyssa@...enzweig.io>, Neal Gompa <neal@...pa.dev>,
 Johan Hedberg <johan.hedberg@...il.com>, Ingo Molnar <mingo@...nel.org>,
 Thomas Gleixner <tglx@...utronix.de>, Al Viro <viro@...iv.linux.org.uk>,
 Kees Cook <kees@...nel.org>, Erick Archer <erick.archer@...look.com>,
 Chris Lu <chris.lu@...iatek.com>, linux-bluetooth@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org,
 linux-arm-kernel@...ts.infradead.org, asahi@...ts.linux.dev
Subject: Re: [PATCH 3/7] Bluetooth: btrtl: Fix typo

Dear Bastien,


Am 03.07.25 um 16:24 schrieb Bastien Nocera:
> Found by codespell.
> 
> Signed-off-by: Bastien Nocera <hadess@...ess.net>
> ---
>   drivers/bluetooth/btrtl.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/bluetooth/btrtl.c b/drivers/bluetooth/btrtl.c
> index 7838c89e529e..3d137944c458 100644
> --- a/drivers/bluetooth/btrtl.c
> +++ b/drivers/bluetooth/btrtl.c
> @@ -693,7 +693,7 @@ static int rtlbt_parse_firmware(struct hci_dev *hdev,
>   
>   	/* Loop from the end of the firmware parsing instructions, until
>   	 * we find an instruction that identifies the "project ID" for the
> -	 * hardware supported by this firwmare file.
> +	 * hardware supported by this firmwmare file.

Without the second m.

>   	 * Once we have that, we double-check that project_id is suitable
>   	 * for the hardware we are working with.
>   	 */


Kind regards,

Paul


PS: Should you resend, it’d be great if you wrote in the summary/title 
if it’s in a comment or in a log string.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ