From: "Paul E. McKenney" <paulmck@kernel.org>
To: Ethon Paul <ethp@qq.com>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] srcu: Fix a typo in comment "amoritized"->"amortized"
Date: Sun, 19 Apr 2020 08:15:27 -0700 [thread overview]
Message-ID: <20200419151527.GT17661@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200418114648.7651-1-ethp@qq.com>
On Sat, Apr 18, 2020 at 07:46:47PM +0800, Ethon Paul wrote:
> There is a typo in comment, fix it.
>
> Signed-off-by: Ethon Paul <ethp@qq.com>
Good eyes!!! Queued, thank you!
I did edit the commit log as shown below. Please let me know if I messed
anything up.
Thanx, Paul
------------------------------------------------------------------------
commit 496c9c0dc7b259ee93ea91789a20e09421e840c1
Author: Ethon Paul <ethp@qq.com>
Date: Sat Apr 18 19:46:47 2020 +0800
srcu: Fix a typo in comment "amoritized"->"amortized"
This commit fixes a typo in a comment.
Signed-off-by: Ethon Paul <ethp@qq.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
diff --git a/kernel/rcu/srcutree.c b/kernel/rcu/srcutree.c
index 6d3ef70..8ff71e5 100644
--- a/kernel/rcu/srcutree.c
+++ b/kernel/rcu/srcutree.c
@@ -766,7 +766,7 @@ static void srcu_flip(struct srcu_struct *ssp)
* it, if this function was preempted for enough time for the counters
* to wrap, it really doesn't matter whether or not we expedite the grace
* period. The extra overhead of a needlessly expedited grace period is
- * negligible when amoritized over that time period, and the extra latency
+ * negligible when amortized over that time period, and the extra latency
* of a needlessly non-expedited grace period is similarly negligible.
*/
static bool srcu_might_be_idle(struct srcu_struct *ssp)
parent reply other threads:[~2020-04-19 15:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200418114648.7651-1-ethp@qq.com>]
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=20200419151527.GT17661@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=ethp@qq.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).