From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Amer Al Shanawany <amer.shanawany@gmail.com>,
Shuah Khan <shuah@kernel.org>,
Christian Brauner <brauner@kernel.org>,
Miklos Szeredi <mszeredi@redhat.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>
Subject: Re: [PATCH] selftests: filesystems: add missing stddef header
Date: Fri, 19 Apr 2024 21:45:06 +0500 [thread overview]
Message-ID: <4b66cfb8-5d42-4432-b930-e23482a48dc6@collabora.com> (raw)
In-Reply-To: <20240417161623.37166-1-amer.shanawany@gmail.com>
On 4/17/24 9:16 PM, Amer Al Shanawany wrote:
> fix compiler warning and errors when compiling statmount test.
The error description or the compiler with version is required to reproduce
the error easily. I'm unable to reproduce the error by gcc 12 and clang 17.
>
> Signed-off-by: Amer Al Shanawany <amer.shanawany@gmail.com>
> ---
> tools/testing/selftests/filesystems/statmount/statmount_test.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/testing/selftests/filesystems/statmount/statmount_test.c b/tools/testing/selftests/filesystems/statmount/statmount_test.c
> index 3eafd7da58e2..e6d7c4f1c85b 100644
> --- a/tools/testing/selftests/filesystems/statmount/statmount_test.c
> +++ b/tools/testing/selftests/filesystems/statmount/statmount_test.c
> @@ -3,6 +3,7 @@
> #define _GNU_SOURCE
>
> #include <assert.h>
> +#include <stddef.h>
> #include <stdint.h>
> #include <sched.h>
> #include <fcntl.h>
--
BR,
Muhammad Usama Anjum
next prev parent reply other threads:[~2024-04-19 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 16:16 [PATCH] selftests: filesystems: add missing stddef header Amer Al Shanawany
2024-04-19 16:45 ` Muhammad Usama Anjum [this message]
2024-04-20 15:56 ` Amer Al Shanawany
2024-04-22 5:17 ` Muhammad Usama Anjum
2024-04-22 13:16 ` [PATCH v2] " Amer Al Shanawany
2024-04-22 13:49 ` Muhammad Usama Anjum
2024-05-04 17:20 ` Amer Al Shanawany
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=4b66cfb8-5d42-4432-b930-e23482a48dc6@collabora.com \
--to=usama.anjum@collabora.com \
--cc=amer.shanawany@gmail.com \
--cc=brauner@kernel.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mszeredi@redhat.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