linux-kernel - Re: [git pull] drm for 6.15-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: <CAHk-=wjcdfrDTjzm6J6T-3fxtVyBG7a_0BXc2=mgOuM6KPFnCg@mail.gmail.com>
Date: Fri, 28 Mar 2025 17:47:45 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Dave Airlie <airlied@...il.com>
Cc: simona.vetter@...ll.ch, dri-devel <dri-devel@...ts.freedesktop.org>, 
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm for 6.15-rc1

On Thu, 27 Mar 2025 at 19:53, Dave Airlie <airlied@...il.com> wrote:
>
> This is the main drm pull request for 6.15. Bit late, but my wife was
> away getting a PhD and kids took over my writing summaries time, and
> fd.o was offline last week which slowed me down a small bit.

Grr. I did the pull, resolved the (trivial) conflicts, but I notice
that this ended up containing the disgusting "hdrtest" crap that

 (a) slows down the build because it's done for a regular allmodconfig
build rather than be some simple thing that you guys can run as needed

 (b) also leaves random 'hdrtest' turds around in the include directories

People already complained separately about this. It should never have
made it to me in this broken form.

Why the heck is this testing being done as a regular part of the build?

And dammit we don't add random turd files for dependencies that then
make the source tree nasty.

The thing that made me notice that it was still there was that "git
status" complains about the stupid turds not being ignored.

But more importantly, those turds also break filename completion! So
no, adding it to gitignore doesn't actually fix the problem, it would
just have made me not notice as quickly.

This thing needs to *die*.

If you want to do that hdrtest thing, do it as part of your *own*
checks. Don't make everybody else see that disgusting thing and have
those turds in their trees.

I'll just disable it by marking it BROKEN for now. You guys can figure
out what you want to do, but no, forcing others to see those things is
not the answer.

I would suggest you *not* make this part of the Kconfig setup and
normal build at all, but be something where *you* can run it as part
of your tests (ie do it as a "make drm-hdrtest" kind of thing, not as
part of regular builds).

                 Linus