From: Shuah Khan <skhan@linuxfoundation.org>
To: cgel.zte@gmail.com, pbonzini@redhat.com
Cc: shuah@kernel.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
chiminghao <chi.minghao@zte.com.cn>,
Zeal Robot <zealci@zte.com.cm>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests:kvm: remove unneeded semicolon
Date: Fri, 19 Nov 2021 16:37:06 -0700 [thread overview]
Message-ID: <f4be7305-e0d8-68d0-68de-0e95e17563e0@linuxfoundation.org> (raw)
In-Reply-To: <20211119023133.2027-1-chi.minghao@zte.com.cn>
On 11/18/21 7:31 PM, cgel.zte@gmail.com wrote:
Missing commit log. Please add one and include information on
how you found this problem and tool output.
> From: chiminghao <chi.minghao@zte.com.cn>
>
> Fix the following coccicheck REVIEW:
> ./tools/testing/selftests/kvm/access_tracking_perf_test.c: REVIEW Unneeded semicolon
>
> Reported-by: Zeal Robot <zealci@zte.com.cm>
> Signed-off-by: chiminghao <chi.minghao@zte.com.cn>
> ---
> tools/testing/selftests/kvm/access_tracking_perf_test.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/kvm/access_tracking_perf_test.c b/tools/testing/selftests/kvm/access_tracking_perf_test.c
> index 5d95113c7b7c..09bf6c6ca11a 100644
> --- a/tools/testing/selftests/kvm/access_tracking_perf_test.c
> +++ b/tools/testing/selftests/kvm/access_tracking_perf_test.c
> @@ -231,7 +231,7 @@ static void *vcpu_thread_main(void *arg)
> case ITERATION_MARK_IDLE:
> mark_vcpu_memory_idle(vm, vcpu_id);
> break;
> - };
> + }
>
> vcpu_last_completed_iteration[vcpu_id] = current_iteration;
> }
>
thanks,
-- Shuah
prev parent reply other threads:[~2021-11-19 23:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 2:31 cgel.zte
2021-11-19 23:37 ` Shuah Khan [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=f4be7305-e0d8-68d0-68de-0e95e17563e0@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=cgel.zte@gmail.com \
--cc=chi.minghao@zte.com.cn \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
--cc=zealci@zte.com.cm \
/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®