linux-kernel - Re: [PULL] drm-fixes for 6.18-rc4

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] [day] [month] [year] [list]

Message-ID: <CAHk-=wgfWAWx1a-yah=bKmoXOHTd8-c-Eof59UDL-06y7HYJhw@mail.gmail.com>
Date: Fri, 31 Oct 2025 14:58:37 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: DRI Development <dri-devel@...ts.freedesktop.org>, LKML <linux-kernel@...r.kernel.org>, 
	Dave Airlie <airlied@...il.com>
Subject: Re: [PULL] drm-fixes for 6.18-rc4

On Fri, 31 Oct 2025 at 14:41, Simona Vetter <simona.vetter@...ll.ch> wrote:
>
> And yes, the tag is a bit wrong, I was asleep (or well more correctly,
> processing some 6.19 -next PRs while this one one was simmering and gotten
> confused).

I was all confused about this comment because I had already edited out
the "for 6.19-rc4" part of the message on auto-pilot when I was going
through the email and was looking for the error and wondering "what is
Simona talking about?"

I had to go back and look at the original tag contents to go "Oh, _that_".

Which shows that I really only start paying attention to version
information during the later part of the release cycle, when pull
requests might be for the next merge window.

During rc3 I just assume it's fixes for the current release and would
only react if the diffstat or the explanations said something else...

                   Linus