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:
 <PN3PR01MB95978C5635B676286A9F0EB7B8B82@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM>
Date: Mon, 21 Apr 2025 18:35:13 +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 05:35 pm, Alyssa Rosenzweig wrote:
>> Can I have a feedback from some DRM maintainer on this? AFAIK merge window is over for some time now. It's been more than a week and last time when I submitted, it just stayed in the mailing list without any feedback.
> 
> DRM hides the merge window from committers so that's not super relevant.
> 
> I am a DRM committer and can pick this up if necessary but it's not
> clear to me what's going thru with DRM vs elsewhere.

All the three patches are intended to go through DRM. IIRC Petr, the vsprintf maintainers had requested for that to be done.

The relevant patches have been Reviewed-by Petr as well.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ