linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: tklauser@distanz.ch
Cc: linux-riscv@lists.infradead.org, aou@eecs.berkeley.edu,
	Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH RESEND] riscv: Fix typo in asm/hwcap.h uapi header
Date: Tue, 14 Jul 2020 10:32:32 -0700 (PDT)	[thread overview]
Message-ID: <mhng-c6c7ebc7-1eb5-49bb-aa60-7375c918fd33@palmerdabbelt-glaptop1> (raw)
In-Reply-To: <20200703134911.4006-1-tklauser@distanz.ch>

On Fri, 03 Jul 2020 06:49:11 PDT (-0700), tklauser@distanz.ch wrote:
> s/userpsace/userspace/
>
> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
> ---
> Resent due to infradead.org mailing list issues.
>
>  arch/riscv/include/uapi/asm/hwcap.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/riscv/include/uapi/asm/hwcap.h b/arch/riscv/include/uapi/asm/hwcap.h
> index dee98ee28318..46dc3f5ee99f 100644
> --- a/arch/riscv/include/uapi/asm/hwcap.h
> +++ b/arch/riscv/include/uapi/asm/hwcap.h
> @@ -11,7 +11,7 @@
>  /*
>   * Linux saves the floating-point registers according to the ISA Linux is
>   * executing on, as opposed to the ISA the user program is compiled for.  This
> - * is necessary for a handful of esoteric use cases: for example, userpsace
> + * is necessary for a handful of esoteric use cases: for example, userspace
>   * threading libraries must be able to examine the actual machine state in
>   * order to fully reconstruct the state of a thread.
>   */

Thanks.  Looks like this one escaped.  It's on for-next now: while it's
trivial, it's not technically a fix and things have started to settle down.

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      reply	other threads:[~2020-07-14 17:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-03 13:49 [PATCH RESEND] riscv: Fix typo in asm/hwcap.h uapi header Tobias Klauser
2020-07-14 17:32 ` Palmer Dabbelt [this message]

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=mhng-c6c7ebc7-1eb5-49bb-aa60-7375c918fd33@palmerdabbelt-glaptop1 \
    --to=palmer@dabbelt.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-riscv@lists.infradead.org \
    --cc=paul.walmsley@sifive.com \
    --cc=tklauser@distanz.ch \
    /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).