linux-kernel - Re: [git pull] drm for 6.10-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CADnq5_Nw_Tr5DABc3XGFpzQhePnVNGW-tzSZAQq0CL=s0iT8sQ@mail.gmail.com>
Date: Thu, 16 May 2024 09:04:44 -0400
From: Alex Deucher <alexdeucher@...il.com>
To: Jani Nikula <jani.nikula@...ux.intel.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Dave Airlie <airlied@...il.com>, 
	Daniel Vetter <daniel.vetter@...ll.ch>, dri-devel <dri-devel@...ts.freedesktop.org>, 
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm for 6.10-rc1

On Thu, May 16, 2024 at 4:42 AM Jani Nikula <jani.nikula@...ux.intel.com> wrote:
>
> On Wed, 15 May 2024, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> > On Wed, 15 May 2024 at 16:17, Dave Airlie <airlied@...il.com> wrote:
> >> AMDGPU, I915 and XE all have !COMPILE_TEST on their variants
> >
> > Hmm.  It turns out that I didn't notice the AMDGPU one because my
> > Threadripper - that has AMDGPU enabled - I have actually turned off
> > EXPERT on, so it's hidden by that for me.
> >
> > But yes, both of those should be "depends on !WERROR" too.
>
> Fair enough. Honestly it just didn't occur to me.
>
> The main goal here was to ensure the drm subsystem does not have any
> build warnings, but without halting CI on any non-drm warnings that
> might occasionally creep in and that we can't fix as quickly.
>
> If there was a way to somehow limit WERROR by subdirectories, without
> config options, I'd love to ditch the config.

Right.  Same thing for amdgpu.  Our CI was often breaking due to
-WERROR in other subsystems or with compiler updates.  Maybe it's
better now.

Alex


>
> > Or maybe they should just go away entirely, and be subsumed by the
> > DRM_WERROR thing.
>
> For i915, this was the idea anyway, we just haven't gotten around to it
> yet.
>
>
> BR,
> Jani.
>
>
> --
> Jani Nikula, Intel