From: Shuah Khan <skhan@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>, Edward Liaw <edliaw@google.com>,
John Hubbard <jhubbard@nvidia.com>
Cc: linux-kselftest@vger.kernel.org, torvalds@linux-foundation.org,
Shuah Khan <skhan@linuxfoundation.org>, shuah <shuah@kernel.org>
Subject: Re: -D_GNU_SOURCE kselftest breakage in mainline
Date: Thu, 16 May 2024 08:53:52 -0600 [thread overview]
Message-ID: <71d1f2bf-2e18-4adb-988f-665675fc803b@linuxfoundation.org> (raw)
In-Reply-To: <d33973a1-4d49-473e-99b6-f0a5174458e7@sirena.org.uk>
On 5/16/24 08:02, Mark Brown wrote:
> Hi,
>
> I'm seeing quite a lot of breakage in mainline as a result of
> daef47b89efd0b7 ("selftests: Compile kselftest headers with
> -D_GNU_SOURCE") and daef47b89efd0 ("selftests: Compile kselftest headers
> with -D_GNU_SOURCE") - thus far I've found that the use of
> static_assert() is triggering build breaks where testsuites aren't
> picking up the addition of _GNU_SOURCE (including stopping installing
> the other tests in the same directory), and there's a bunch of tests
> which #define _GNU_SOURCE in their code and now trigger build warnings.
> I'm looking at fixes and mitigations now.
>
Would it be better to revert this for now and get this for now? I wouldn't
want you to extra busy work to workaround this.
> The build failures are taking out the ALSA tests entirely which has
> caused my personal CI to explode badly :/
>
This has been in next for a while and I didn't see any failures. These
kind of changes are tricky. On second thought, I probably should have
delayed picking this up.
thanks,
-- Shuah
next prev parent reply other threads:[~2024-05-16 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 14:02 -D_GNU_SOURCE kselftest breakage in mainline Mark Brown
2024-05-16 14:53 ` Shuah Khan [this message]
2024-05-16 15:09 ` Mark Brown
2024-05-17 3:41 ` 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=71d1f2bf-2e18-4adb-988f-665675fc803b@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=edliaw@google.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=torvalds@linux-foundation.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