linux-kernel - Re: [PATCH] watchdog: wdat

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] [day] [month] [year] [list]

Date:   Tue, 16 Feb 2021 07:15:37 -0800
From:   Guenter Roeck <linux@...ck-us.net>
To:     Flavio Suligoi <f.suligoi@...m.it>,
        Wim Van Sebroeck <wim@...ux-watchdog.org>,
        Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc:     linux-watchdog@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] watchdog: wdat_wdg: fix typo

On 2/16/21 6:17 AM, Flavio Suligoi wrote:
> Fix the following typo:
> 
> "recommeded" --> "recommended"
> "firmare"    --> "firmware"
> 
> Signed-off-by: Flavio Suligoi <f.suligoi@...m.it>

Reviewed-by: Guenter Roeck <linux@...ck-us.net>

> ---
>  drivers/watchdog/wdat_wdt.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/watchdog/wdat_wdt.c b/drivers/watchdog/wdat_wdt.c
> index cec7917790e5..195c8c004b69 100644
> --- a/drivers/watchdog/wdat_wdt.c
> +++ b/drivers/watchdog/wdat_wdt.c
> @@ -208,7 +208,7 @@ static int wdat_wdt_enable_reboot(struct wdat_wdt *wdat)
>  	/*
>  	 * WDAT specification says that the watchdog is required to reboot
>  	 * the system when it fires. However, it also states that it is
> -	 * recommeded to make it configurable through hardware register. We
> +	 * recommended to make it configurable through hardware register. We
>  	 * enable reboot now if it is configurable, just in case.
>  	 */
>  	ret = wdat_wdt_run_action(wdat, ACPI_WDAT_SET_REBOOT, 0, NULL);
> @@ -475,7 +475,7 @@ static int wdat_wdt_suspend_noirq(struct device *dev)
>  		return 0;
>  
>  	/*
> -	 * We need to stop the watchdog if firmare is not doing it or if we
> +	 * We need to stop the watchdog if firmware is not doing it or if we
>  	 * are going suspend to idle (where firmware is not involved). If
>  	 * firmware is stopping the watchdog we kick it here one more time
>  	 * to give it some time.
>