From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Yu Zhe <yuzhe@nfschina.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Pavel Begunkov <asml.silence@gmail.com>,
io-uring Mailing List <io-uring@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org, liqiong@nfschina.com
Subject: Re: [PATCH] io_uring: fix some spelling mistakes in comment
Date: Fri, 6 Jan 2023 16:35:39 +0700 [thread overview]
Message-ID: <Y7fra/JE003tcpQq@integral2> (raw)
In-Reply-To: <20230106091242.20288-1-yuzhe@nfschina.com>
On Fri, Jan 06, 2023 at 05:12:42PM +0800, Yu Zhe wrote:
> @@ -2822,7 +2822,7 @@ static __cold void io_tctx_exit_cb(struct callback_head *cb)
> * When @in_idle, we're in cancellation and it's racy to remove the
> * node. It'll be removed by the end of cancellation, just ignore it.
> * tctx can be NULL if the queueing of this task_work raced with
> - * work cancelation off the exec path.
> + * work cancellation off the exec path.
> */
> if (tctx && !atomic_read(&tctx->in_idle))
> io_uring_del_tctx_node((unsigned long)work->ctx);
> @@ -3095,7 +3095,7 @@ __cold void io_uring_cancel_generic(bool cancel_all, struct io_sq_data *sqd)
> bool loop = false;
>
> io_uring_drop_tctx_refs(current);
> - /* read completions before cancelations */
> + /* read completions before cancellations */
"cancelations" is not a typo.
"cancelations" and "cancellations" are both valid spellings. The former
is predominantly used in the US, while the latter is predominantly used
in the UK.
--
Ammar Faizi
next prev parent reply other threads:[~2023-01-06 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 9:12 [PATCH] io_uring: fix some spelling mistakes in comment Yu Zhe
2023-01-06 9:35 ` Ammar Faizi [this message]
2023-01-06 9:51 ` Dan Carpenter
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=Y7fra/JE003tcpQq@integral2 \
--to=ammarfaizi2@gnuweeb.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liqiong@nfschina.com \
--cc=yuzhe@nfschina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.