From: Shuah Khan <skhan@linuxfoundation.org>
To: SurajSonawane2415 <surajsonawane0215@gmail.com>,
shuah@kernel.org, "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests/vdso: Add linux/sched.h to fix CLONE_NEWTIME build error
Date: Wed, 2 Oct 2024 16:39:41 -0600 [thread overview]
Message-ID: <543d4b19-e530-45e3-876c-522101f9a5e6@linuxfoundation.org> (raw)
In-Reply-To: <20241002152849.111841-1-surajsonawane0215@gmail.com>
On 10/2/24 09:28, SurajSonawane2415 wrote:
> Fix build error in vdso_test_getrandom.c due to missing CLONE_NEWTIME.
> Include linux/sched.h to define CLONE_NEWTIME.
> Ensure successful compilation by resolving the missing header issue.
>
Did you run "make headers" before building this test? It builds
just fine for me on my system.
+ Adding Jason Donenfeld
> Signed-off-by: SurajSonawane2415 <surajsonawane0215@gmail.com>
> ---
> tools/testing/selftests/vDSO/vdso_test_getrandom.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/testing/selftests/vDSO/vdso_test_getrandom.c b/tools/testing/selftests/vDSO/vdso_test_getrandom.c
> index 72a1d9b43..3f2a4dbf8 100644
> --- a/tools/testing/selftests/vDSO/vdso_test_getrandom.c
> +++ b/tools/testing/selftests/vDSO/vdso_test_getrandom.c
> @@ -22,6 +22,7 @@
> #include <linux/random.h>
> #include <linux/compiler.h>
> #include <linux/ptrace.h>
> +#include <linux/sched.h>
>
> #include "../kselftest.h"
> #include "parse_vdso.h"
thanks,
-- Shuah
next prev parent reply other threads:[~2024-10-02 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 15:28 [PATCH] selftests/vdso: Add linux/sched.h to fix CLONE_NEWTIME build error SurajSonawane2415
2024-10-02 22:39 ` Shuah Khan [this message]
2024-10-02 22:51 ` Jason A. Donenfeld
2024-10-03 22:26 ` Shuah Khan
2024-10-03 11:52 ` [PATCH] selftests: vDSO: fix compile error for vdso_test_getrandom SurajSonawane2415
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=543d4b19-e530-45e3-876c-522101f9a5e6@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=Jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=surajsonawane0215@gmail.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