From: Shuah Khan <skhan@linuxfoundation.org>
To: aigourensheng <shechenglong001@gmail.com>, shuah@kernel.org
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests/sched: fix code format issues
Date: Tue, 11 Jun 2024 14:48:50 -0600 [thread overview]
Message-ID: <d6c5ba89-065b-43d5-8584-0c1effa50c07@linuxfoundation.org> (raw)
In-Reply-To: <20240611051834.2885-1-shechenglong001@gmail.com>
On 6/10/24 23:18, aigourensheng wrote:
> There are extra spaces in the middle of #define. It is recommended
> to delete the spaces to make the code look more comfortable.
>
> Signed-off-by: aigourensheng <shechenglong001@gmail.com>
> ---
> tools/testing/selftests/sched/cs_prctl_test.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/tools/testing/selftests/sched/cs_prctl_test.c b/tools/testing/selftests/sched/cs_prctl_test.c
> index 62fba7356af2..52d97fae4dbd 100644
> --- a/tools/testing/selftests/sched/cs_prctl_test.c
> +++ b/tools/testing/selftests/sched/cs_prctl_test.c
> @@ -42,11 +42,11 @@ static pid_t gettid(void)
>
> #ifndef PR_SCHED_CORE
> #define PR_SCHED_CORE 62
> -# define PR_SCHED_CORE_GET 0
> -# define PR_SCHED_CORE_CREATE 1 /* create unique core_sched cookie */
> -# define PR_SCHED_CORE_SHARE_TO 2 /* push core_sched cookie to pid */
> -# define PR_SCHED_CORE_SHARE_FROM 3 /* pull core_sched cookie to pid */
> -# define PR_SCHED_CORE_MAX 4
> +#define PR_SCHED_CORE_GET 0
> +#define PR_SCHED_CORE_CREATE 1 /* create unique core_sched cookie */
> +#define PR_SCHED_CORE_SHARE_TO 2 /* push core_sched cookie to pid */
> +#define PR_SCHED_CORE_SHARE_FROM 3 /* pull core_sched cookie to pid */
> +#define PR_SCHED_CORE_MAX 4
> #endif
>
> #define MAX_PROCESSES 128
Applied to linux-ksleftest next for Linux 6.11-rc1
thanks,
-- Shuah
prev parent reply other threads:[~2024-06-11 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 5:18 [PATCH] selftests/sched: fix code format issues aigourensheng
2024-06-11 20:48 ` 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=d6c5ba89-065b-43d5-8584-0c1effa50c07@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shechenglong001@gmail.com \
--cc=shuah@kernel.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