From: Randy Dunlap <rdunlap@infradead.org>
To: cgel.zte@gmail.com, tj@kernel.org
Cc: lizefan.x@bytedance.com, hannes@cmpxchg.org, corbet@lwn.net,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
lufengchang <lu.fengchang@zte.com.cn>,
Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH linux-next] admin-guide: cgroup: fix a typo in description
Date: Thu, 25 Aug 2022 19:48:10 -0700 [thread overview]
Message-ID: <795c6785-e13e-5322-15b3-60ee2ec24197@infradead.org> (raw)
In-Reply-To: <20220826020552.239407-1-lu.fengchang@zte.com.cn>
Hi,
On 8/25/22 19:05, cgel.zte@gmail.com wrote:
> From: lufengchang <lu.fengchang@zte.com.cn>
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: lufengchang <lu.fengchang@zte.com.cn>
Are you sure that it's a typo?
https://en.wikipedia.org/wiki/If_and_only_if
"iff" is commonly used (in math/technical literature)
to mean "if and only if".
> ---
> Documentation/admin-guide/cgroup-v1/cgroups.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/cgroup-v1/cgroups.rst b/Documentation/admin-guide/cgroup-v1/cgroups.rst
> index b0688011ed06..fa747466e304 100644
> --- a/Documentation/admin-guide/cgroup-v1/cgroups.rst
> +++ b/Documentation/admin-guide/cgroup-v1/cgroups.rst
> @@ -573,7 +573,7 @@ cgroup_for_each_descendant_pre() for details.
> ``void css_offline(struct cgroup *cgrp);``
> (cgroup_mutex held by caller)
>
> -This is the counterpart of css_online() and called iff css_online()
> +This is the counterpart of css_online() and called if css_online()
> has succeeded on @cgrp. This signifies the beginning of the end of
> @cgrp. @cgrp is being removed and the subsystem should start dropping
> all references it's holding on @cgrp. When all references are dropped,
--
~Randy
prev parent reply other threads:[~2022-08-26 2:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 2:05 [PATCH linux-next] admin-guide: cgroup: fix a typo in description cgel.zte
2022-08-26 2:48 ` Randy Dunlap [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=795c6785-e13e-5322-15b3-60ee2ec24197@infradead.org \
--to=rdunlap@infradead.org \
--cc=cgel.zte@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=lu.fengchang@zte.com.cn \
--cc=tj@kernel.org \
--cc=zealci@zte.com.cn \
/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