public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Charlie Jenkins <charlie@rivosinc.com>
To: Chin Yik Ming <yikming2222@gmail.com>
Cc: palmer@dabbelt.com, paul.walmsley@sifive.com,
	aou@eecs.berkeley.edu, alexghiti@rivosinc.com,
	samuel.holland@sifive.com, parri.andrea@gmail.com,
	atishp@rivosinc.com, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: Fix a comment typo in set_mm_asid()
Date: Thu, 14 Nov 2024 14:08:47 -0800	[thread overview]
Message-ID: <ZzZ072CMku0fsW2x@ghost> (raw)
In-Reply-To: <20241114212725.4172401-1-yikming2222@gmail.com>

On Fri, Nov 15, 2024 at 05:27:25AM +0800, Chin Yik Ming wrote:
> s/verion/version
> 
> Signed-off-by: Chin Yik Ming <yikming2222@gmail.com>
> ---
>  arch/riscv/mm/context.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/riscv/mm/context.c b/arch/riscv/mm/context.c
> index 4abe3de23225..55c20ad1f744 100644
> --- a/arch/riscv/mm/context.c
> +++ b/arch/riscv/mm/context.c
> @@ -158,7 +158,7 @@ static void set_mm_asid(struct mm_struct *mm, unsigned int cpu)
>  	 *
>  	 * - We get a zero back from the cmpxchg and end up waiting on the
>  	 *   lock. Taking the lock synchronises with the rollover and so
> -	 *   we are forced to see the updated verion.
> +	 *   we are forced to see the updated version.
>  	 *
>  	 * - We get a valid context back from the cmpxchg then we continue
>  	 *   using old ASID because __flush_context() would have marked ASID
> -- 
> 2.34.1
> 

Thanks,

Reviewed-by: Charlie Jenkins <charlie@rivosinc.com>


  reply	other threads:[~2024-11-14 22:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 21:27 [PATCH] riscv: Fix a comment typo in set_mm_asid() Chin Yik Ming
2024-11-14 22:08 ` Charlie Jenkins [this message]
2025-03-27  3:25 ` patchwork-bot+linux-riscv

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=ZzZ072CMku0fsW2x@ghost \
    --to=charlie@rivosinc.com \
    --cc=alexghiti@rivosinc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=atishp@rivosinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=parri.andrea@gmail.com \
    --cc=paul.walmsley@sifive.com \
    --cc=samuel.holland@sifive.com \
    --cc=yikming2222@gmail.com \
    /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