linux-kernel - Re: [PATCH] tools: include: nolibc: Fix a typo occured to occurred in the file nolibc.h

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: <3a9e310f-2a5b-9fc2-cd5a-222e2ed353e4@infradead.org>
Date:   Sat, 27 Feb 2021 14:58:18 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Bhaskar Chowdhury <unixbhaskar@...il.com>, w@....eu,
        paul.walmsley@...ive.com, palmer@...belt.com,
        aou@...s.berkeley.edu, linux-kernel@...r.kernel.org,
        linux-riscv@...ts.infradead.org
Cc:     colin.king@...onical.com
Subject: Re: [PATCH] tools: include: nolibc: Fix a typo occured to occurred in
 the file nolibc.h

On 2/27/21 2:44 PM, Bhaskar Chowdhury wrote:
> 
> s/occured/occurred/
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>

Acked-by: Randy Dunlap <rdunlap@...radead.org>


> ---
>  Stolen result from Colin's finding and share from the other places. :)
> 
>  tools/include/nolibc/nolibc.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/include/nolibc/nolibc.h b/tools/include/nolibc/nolibc.h
> index e61d36cd4e50..fc998c359607 100644
> --- a/tools/include/nolibc/nolibc.h
> +++ b/tools/include/nolibc/nolibc.h
> @@ -1054,7 +1054,7 @@ struct sys_stat_struct {
>   *     scall32-o32.S in the kernel sources.
>   *   - the system call is performed by calling "syscall"
>   *   - syscall return comes in v0, and register a3 needs to be checked to know
> - *     if an error occured, in which case errno is in v0.
> + *     if an error occurred, in which case errno is in v0.
>   *   - the arguments are cast to long and assigned into the target registers
>   *     which are then simply passed as registers to the asm code, so that we
>   *     don't have to experience issues with register constraints.
> --


-- 
~Randy