From: Michael Ellerman <mpe@ellerman.id.au>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>,
linux-kselftest@vger.kernel.org, skhan@linuxfoundation.org
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Muhammad Usama Anjum <usama.anjum@collabora.com>
Subject: Re: [PATCH] selftests/openat2: Fix build warnings on ppc64
Date: Wed, 29 May 2024 18:23:13 +1000 [thread overview]
Message-ID: <87bk4p3u32.fsf@mail.lhotse> (raw)
In-Reply-To: <94964224-1796-4610-a42d-3aacb4d47341@collabora.com>
Muhammad Usama Anjum <usama.anjum@collabora.com> writes:
> I was looking at if we can add this flag for ppc64 for all selftests
> somewhere. But there isn't any suitable place other than in KHDR_INCLUDES.
> But there is a series already trying to add _GNU_SOURCE to it.
IMHO adding other flags to KHDR_INCLUDES is not the right solution, it
conflates unrelated things. Some tests may want the kernel headers but
not _GNU_SOURCE, or vice versa.
Adding a separate define for "standard kselftest flags" would be
preferable, and then something like __SANE_USERSPACE_TYPES__ would make
sense being added to it.
> Reviewed-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
Thanks.
cheers
> On 5/20/24 8:03 PM, Michael Ellerman wrote:
>> Fix warnings like:
>>
>> openat2_test.c: In function ‘test_openat2_flags’:
>> openat2_test.c:303:73: warning: format ‘%llX’ expects argument of type
>> ‘long long unsigned int’, but argument 5 has type ‘__u64’ {aka ‘long
>> unsigned int’} [-Wformat=]
>>
>> By switching to unsigned long long for u64 for ppc64 builds.
>>
>> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
>> ---
>> tools/testing/selftests/openat2/openat2_test.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/tools/testing/selftests/openat2/openat2_test.c b/tools/testing/selftests/openat2/openat2_test.c
>> index 9024754530b2..5790ab446527 100644
>> --- a/tools/testing/selftests/openat2/openat2_test.c
>> +++ b/tools/testing/selftests/openat2/openat2_test.c
>> @@ -5,6 +5,7 @@
>> */
>>
>> #define _GNU_SOURCE
>> +#define __SANE_USERSPACE_TYPES__ // Use ll64
>> #include <fcntl.h>
>> #include <sched.h>
>> #include <sys/stat.h>
>
> --
> BR,
> Muhammad Usama Anjum
next prev parent reply other threads:[~2024-05-29 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 3:03 [PATCH] selftests/openat2: Fix build warnings on ppc64 Michael Ellerman
2024-05-25 4:32 ` Muhammad Usama Anjum
2024-05-29 8:23 ` Michael Ellerman [this message]
2024-05-29 22:20 ` Shuah Khan
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=87bk4p3u32.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=skhan@linuxfoundation.org \
--cc=usama.anjum@collabora.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;
as well as URLs for NNTP newsgroup(s).