linux-kernel - Re: linux-next: manual merge of the drm-xe tree with the mm tree

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: <20250311180202.058334d5@canb.auug.org.au>
Date: Tue, 11 Mar 2025 18:02:02 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Alistair Popple <apopple@...dia.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, Dave Airlie
 <airlied@...hat.com>, Lucas De Marchi <lucas.demarchi@...el.com>, Thomas
 Hellström <thomas.hellstrom@...ux.intel.com>, DRM XE
 List <intel-xe@...ts.freedesktop.org>, Balbir Singh <balbirs@...dia.com>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
 Mailing List <linux-next@...r.kernel.org>, Matthew Brost
 <matthew.brost@...el.com>, DRI <dri-devel@...ts.freedesktop.org>
Subject: Re: linux-next: manual merge of the drm-xe tree with the mm tree

Hi Alistair,

On Tue, 11 Mar 2025 16:57:49 +1100 Alistair Popple <apopple@...dia.com> wrote:
>
> I'm not sure what the process is here, but having either reviewed or authored
> these patches I can add that the fix up carried below looks correct.

Thanks.  This means that people can have a bit more confidence in the
resulting linux-next tree (and so can I :-)) and when the merge
requests are sent to Linus, they can just reference my resolution.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped