From: Dmitry Ilvokhin <d@ilvokhin.com>
To: Xiang Gao <gxxa03070307@gmail.com>
Cc: peterz@infradead.org, mingo@redhat.com, will@kernel.org,
boqun@kernel.org, longman@redhat.com,
linux-kernel@vger.kernel.org, Xiang Gao <gaoxiang17@xiaomi.com>
Subject: Re: [PATCH] locking: fix typos in comments
Date: Thu, 16 Apr 2026 15:11:01 +0000 [thread overview]
Message-ID: <aeD8BWOAB6ZeNFMZ@shell.ilvokhin.com> (raw)
In-Reply-To: <20260416090407.930301-1-gxxa03070307@gmail.com>
On Thu, Apr 16, 2026 at 05:04:07PM +0800, Xiang Gao wrote:
> From: Xiang Gao <gaoxiang17@xiaomi.com>
>
> Fix the following typos in comments:
>
> mutex.c: "crital" -> "critical" (2 instances)
> mutex.c: "task_strcut" -> "task_struct" (2 instances)
> rwsem.c: "Otherwisee" -> "Otherwise"
> rwsem.c: "crital" -> "critical" (2 instances)
> rwsem.c: "task_strcut" -> "task_struct"
>
> Signed-off-by: Xiang Gao <gaoxiang17@xiaomi.com>
Reviewed-by: Dmitry Ilvokhin <d@ilvokhin.com>
prev parent reply other threads:[~2026-04-16 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 9:04 [PATCH] locking: fix typos in comments Xiang Gao
2026-04-16 15:06 ` Waiman Long
2026-04-16 15:11 ` Dmitry Ilvokhin [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=aeD8BWOAB6ZeNFMZ@shell.ilvokhin.com \
--to=d@ilvokhin.com \
--cc=boqun@kernel.org \
--cc=gaoxiang17@xiaomi.com \
--cc=gxxa03070307@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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