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]

Date: Wed, 15 May 2024 16:58:09 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Dave Airlie <airlied@...il.com>
Cc: Jani Nikula <jani.nikula@...ux.intel.com>, Jani Nikula <jani.nikula@...el.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 Wed, 15 May 2024 at 16:17, Dave Airlie <airlied@...il.com> wrote:
>
> It's also possible it's just that hey there's a few others in the tree
>
> KVM_WERROR not tied to it
> PPC_WERROR (why does CXL uses this?)

Yeah, that should be fixed too, but at least KVM_WERROR predates the
whole-kernel WERROR.

And PPC_WERROR predates it by over a decade.

But yes, good catch - both of those should be silenced if we already
have the global WERROR enabled.

I mainly notice new questions (because I use "make oldconfig"), so old
pre-existing illogical ones don't trigger my "why are they asking?"
reaction.

> 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.

Or maybe they should just go away entirely, and be subsumed by the
DRM_WERROR thing.

               Linus