From: Mukesh Ojha <quic_mojha@quicinc.com>
To: wangjianli <wangjianli@cdjrlc.com>, <tj@kernel.org>,
<lizefan.x@bytedance.com>, <hannes@cmpxchg.org>,
<shuah@kernel.org>
Cc: <cgroups@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] selftests/cgroup: fix repeated words in comments
Date: Thu, 8 Sep 2022 19:22:07 +0530 [thread overview]
Message-ID: <36d3af06-4534-000f-525d-d1fa82467aaa@quicinc.com> (raw)
In-Reply-To: <20220908121107.4814-1-wangjianli@cdjrlc.com>
Hi,
On 9/8/2022 5:41 PM, wangjianli wrote:
> Delete the redundant word 'in'.
>
> Signed-off-by: wangjianli <wangjianli@cdjrlc.com>
> ---
> tools/testing/selftests/cgroup/test_freezer.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/cgroup/test_freezer.c b/tools/testing/selftests/cgroup/test_freezer.c
> index ff519029f6f4..b479434e87b7 100644
> --- a/tools/testing/selftests/cgroup/test_freezer.c
> +++ b/tools/testing/selftests/cgroup/test_freezer.c
> @@ -740,7 +740,7 @@ static int test_cgfreezer_ptraced(const char *root)
>
> /*
> * cg_check_frozen(cgroup, true) will fail here,
> - * because the task in in the TRACEd state.
> + * because the task in the TRACEd state.
Should it be s/in in/is in/ ?
-Mukesh
> */
> if (cg_freeze_wait(cgroup, false))
> goto cleanup;
next prev parent reply other threads:[~2022-09-08 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 12:11 wangjianli
2022-09-08 13:52 ` Mukesh Ojha [this message]
2022-09-08 13:52 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2022-07-24 7:04 wangjianli
2022-07-24 15:52 ` Joe Perches
2022-07-25 5:47 ` Mukesh Ojha
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=36d3af06-4534-000f-525d-d1fa82467aaa@quicinc.com \
--to=quic_mojha@quicinc.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=shuah@kernel.org \
--cc=tj@kernel.org \
--cc=wangjianli@cdjrlc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®