mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
	w@1wt.eu, paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org
Cc: colin.king@canonical.com
Subject: Re: [PATCH] tools: include: nolibc: Fix a typo occured to occurred in the file nolibc.h
Date: Sat, 27 Feb 2021 14:58:18 -0800	[thread overview]
Message-ID: <3a9e310f-2a5b-9fc2-cd5a-222e2ed353e4@infradead.org> (raw)
In-Reply-To: <20210227224435.21315-1-unixbhaskar@gmail.com>

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

Acked-by: Randy Dunlap <rdunlap@infradead.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


  reply	other threads:[~2021-02-27 22:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-27 22:44 Bhaskar Chowdhury
2021-02-27 22:58 ` Randy Dunlap [this message]
2021-03-22  6:43   ` Willy Tarreau

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=3a9e310f-2a5b-9fc2-cd5a-222e2ed353e4@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=colin.king@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=unixbhaskar@gmail.com \
    --cc=w@1wt.eu \
    /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

all inboxes | Powered by JetHome®