From: Shuah Khan <skhan@linuxfoundation.org>
To: Zhu Jun <zhujun2@cmss.chinamobile.com>, shuah@kernel.org
Cc: angquan21@gmail.com, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2] selftests/breakpoints:Add return value in main function
Date: Wed, 10 Jul 2024 09:47:31 -0600 [thread overview]
Message-ID: <10a36c82-3c74-4fc3-abce-b2fe81956d37@linuxfoundation.org> (raw)
In-Reply-To: <20240710021605.2900-1-zhujun2@cmss.chinamobile.com>
On 7/9/24 20:16, Zhu Jun wrote:
> Main function return value is int type, so add return
> value in the end that this problem was discovered by reading the code
>
> Signed-off-by: Zhu Jun <zhujun2@cmss.chinamobile.com>
> ---
> Changes in v2:
> - modify commit info
>
> tools/testing/selftests/breakpoints/step_after_suspend_test.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/breakpoints/step_after_suspend_test.c b/tools/testing/selftests/breakpoints/step_after_suspend_test.c
> index dfec31fb9b30..b473131fce3e 100644
> --- a/tools/testing/selftests/breakpoints/step_after_suspend_test.c
> +++ b/tools/testing/selftests/breakpoints/step_after_suspend_test.c
> @@ -166,7 +166,7 @@ int main(int argc, char **argv)
> bool succeeded = true;
> unsigned int tests = 0;
> cpu_set_t available_cpus;
> - int err;
> + int err = 0;
> int cpu;
>
> ksft_print_header();
> @@ -222,4 +222,6 @@ int main(int argc, char **argv)
> ksft_exit_pass();
> else
> ksft_exit_fail();
> +
> + return err;
> }
Unless this is causing a compile error or warning - there is
no need to make this change.
thanks,
-- Shuah
prev parent reply other threads:[~2024-07-10 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 2:16 [PATCH v2] selftests/breakpoints:Add return value in main function Zhu Jun
2024-07-10 15:47 ` 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=10a36c82-3c74-4fc3-abce-b2fe81956d37@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=angquan21@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=zhujun2@cmss.chinamobile.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