linux-kernel - Re: [PATCH v4 0/3] Use proper printk format in appletbdrm

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 for Android: free password hash cracker in your pocket

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

Message-ID:
 <PN3PR01MB95976FC24DDF82A084079C37B8B82@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM>
Date: Mon, 21 Apr 2025 19:28:57 +0530
From: Aditya Garg <gargaditya08@...e.com>
To: Alyssa Rosenzweig <alyssa@...enzweig.io>
Cc: Petr Mladek <pmladek@...e.com>,
 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
 Sven Peter <sven@...npeter.dev>, Thomas Zimmermann <tzimmermann@...e.de>,
 Aun-Ali Zaidi <admin@...eit.net>, Maxime Ripard <mripard@...nel.org>,
 airlied@...hat.com, Simona Vetter <simona@...ll.ch>,
 Steven Rostedt <rostedt@...dmis.org>,
 Rasmus Villemoes <linux@...musvillemoes.dk>,
 Sergey Senozhatsky <senozhatsky@...omium.org>,
 Jonathan Corbet <corbet@....net>, Andrew Morton <akpm@...ux-foundation.org>,
 apw@...onical.com, joe@...ches.com, dwaipayanray1@...il.com,
 lukas.bulwahn@...il.com, Kees Cook <kees@...nel.org>, tamird@...il.com,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 dri-devel@...ts.freedesktop.org, linux-doc@...r.kernel.org,
 Hector Martin <marcan@...can.st>,
 Asahi Linux Mailing List <asahi@...ts.linux.dev>
Subject: Re: [PATCH v4 0/3] Use proper printk format in appletbdrm



On 21-04-2025 07:26 pm, Alyssa Rosenzweig wrote:
>> Any change needed or just because some other maintainer manages this? Although Tbh, I really don't care about backporting since T2 Mac users are still using patched kernels provided by us. I'd rather free my mind in getting this done.
> 
> I'm just too new to kernel to do nontrivial merges. Either I can queue
> this series to drm-misc-next today (no backport no changes) or we can
> wait for someone more experienced. Let me know which one.

Merge it to drm-misc-next. I am totally ok with that.