public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Yuu Lee <379943137@qq.com>
Cc: peterz@infradead.org, mingo@redhat.com, will@kernel.org,
	longman@redhat.com, boqun.feng@gmail.com,
	linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] locking/mutex: fix documentation spelling mistakes
Date: Wed, 13 Mar 2024 11:22:35 +0100	[thread overview]
Message-ID: <ZfF+a4ZpEBjxmXtt@gmail.com> (raw)
In-Reply-To: <tencent_8E6B496F6B4EC012379A594046F8880B3D08@qq.com>


* Yuu Lee <379943137@qq.com> wrote:

> fix 'task_strcut' to 'task_struct'
> 
> Signed-off-by: Yuu Lee <379943137@qq.com>
> ---
>  kernel/locking/mutex.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/locking/mutex.c b/kernel/locking/mutex.c
> index cbae8c0b8..82d19846e 100644
> --- a/kernel/locking/mutex.c
> +++ b/kernel/locking/mutex.c
> @@ -362,7 +362,7 @@ bool mutex_spin_on_owner(struct mutex *lock, struct task_struct *owner,
>  		 * checking lock->owner still matches owner. And we already
>  		 * disabled preemption which is equal to the RCU read-side
>  		 * crital section in optimistic spinning code. Thus the
> -		 * task_strcut structure won't go away during the spinning
> +		 * task_struct structure won't go away during the spinning
>  		 * period
>  		 */
>  		barrier();
> @@ -401,7 +401,7 @@ static inline int mutex_can_spin_on_owner(struct mutex *lock)
>  
>  	/*
>  	 * We already disabled preemption which is equal to the RCU read-side
> -	 * crital section in optimistic spinning code. Thus the task_strcut
> +	 * crital section in optimistic spinning code. Thus the task_struct
>  	 * structure won't go away during the spinning period.

There's another typo here, which you might as well fix?

Thanks,

	Ingo

      reply	other threads:[~2024-03-13 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13  9:02 [PATCH] locking/mutex: fix documentation spelling mistakes Yuu Lee
2024-03-13 10:22 ` Ingo Molnar [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=ZfF+a4ZpEBjxmXtt@gmail.com \
    --to=mingo@kernel.org \
    --cc=379943137@qq.com \
    --cc=boqun.feng@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=trivial@kernel.org \
    --cc=will@kernel.org \
    /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