From: Alyssa Rosenzweig <alyssa@rosenzweig.io>
To: Aditya Garg <gargaditya08@live.com>
Cc: Petr Mladek <pmladek@suse.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Sven Peter <sven@svenpeter.dev>,
Thomas Zimmermann <tzimmermann@suse.de>,
Aun-Ali Zaidi <admin@kodeit.net>,
Maxime Ripard <mripard@kernel.org>,
airlied@redhat.com, Simona Vetter <simona@ffwll.ch>,
Steven Rostedt <rostedt@goodmis.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
apw@canonical.com, joe@perches.com, dwaipayanray1@gmail.com,
lukas.bulwahn@gmail.com, Kees Cook <kees@kernel.org>,
tamird@gmail.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
Hector Martin <marcan@marcan.st>,
Asahi Linux Mailing List <asahi@lists.linux.dev>
Subject: Re: [PATCH v4 0/3] Use proper printk format in appletbdrm
Date: Mon, 21 Apr 2025 09:56:52 -0400 [thread overview]
Message-ID: <aAZOpLeqBeeZ-4mG@blossom> (raw)
In-Reply-To: <PN3PR01MB95973648BB4FECBB2E24C5C7B8B82@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM>
> 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.
next prev parent reply other threads:[~2025-04-21 13:57 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 6:47 [PATCH v4 0/3] Use proper printk format in appletbdrm Aditya Garg
2025-04-08 6:47 ` [PATCH v4 1/3] lib/vsprintf: Add support for generic FourCCs by extending %p4cc Aditya Garg
2025-04-08 6:49 ` [PATCH v4 3/3] drm/appletbdrm: use %p4cl instead of %p4cc Aditya Garg
2025-04-08 21:56 ` [PATCH v4 1/3] lib/vsprintf: Add support for generic FourCCs by extending %p4cc Kees Cook
2025-04-22 8:07 ` Geert Uytterhoeven
2025-04-22 8:29 ` Aditya Garg
2025-04-22 8:43 ` Geert Uytterhoeven
2025-04-22 9:41 ` Aditya Garg
2025-04-22 10:16 ` Andy Shevchenko
2025-04-22 10:32 ` Geert Uytterhoeven
2025-04-22 15:15 ` Aditya Garg
2025-04-22 15:22 ` Andy Shevchenko
2025-04-22 15:28 ` Aditya Garg
2025-04-22 15:17 ` Andy Shevchenko
2025-04-23 13:39 ` Petr Mladek
2025-04-23 13:47 ` Aditya Garg
2025-04-23 14:50 ` Geert Uytterhoeven
2025-04-23 16:29 ` Andy Shevchenko
2025-04-23 17:46 ` Geert Uytterhoeven
2025-04-22 10:12 ` Andy Shevchenko
2025-04-22 10:20 ` Geert Uytterhoeven
2025-04-08 6:48 ` [PATCH v4 2/3] printf: add tests for generic FourCCs Aditya Garg
2025-04-08 21:56 ` Kees Cook
2025-04-08 8:41 ` [PATCH v4 0/3] Use proper printk format in appletbdrm Andy Shevchenko
2025-04-08 8:52 ` Aditya Garg
2025-04-08 9:38 ` Andy Shevchenko
2025-04-09 15:30 ` Petr Mladek
2025-04-17 13:53 ` Aditya Garg
2025-04-21 12:05 ` Alyssa Rosenzweig
2025-04-21 13:05 ` Aditya Garg
2025-04-21 13:07 ` Alyssa Rosenzweig
2025-04-21 13:08 ` Aditya Garg
2025-04-21 13:10 ` Aditya Garg
2025-04-21 13:49 ` Alyssa Rosenzweig
2025-04-21 13:54 ` Aditya Garg
2025-04-21 13:56 ` Alyssa Rosenzweig [this message]
2025-04-21 13:58 ` Aditya Garg
2025-04-21 14:30 ` Alyssa Rosenzweig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aAZOpLeqBeeZ-4mG@blossom \
--to=alyssa@rosenzweig.io \
--cc=admin@kodeit.net \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=apw@canonical.com \
--cc=asahi@lists.linux.dev \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=dwaipayanray1@gmail.com \
--cc=gargaditya08@live.com \
--cc=joe@perches.com \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=lukas.bulwahn@gmail.com \
--cc=marcan@marcan.st \
--cc=mripard@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=simona@ffwll.ch \
--cc=sven@svenpeter.dev \
--cc=tamird@gmail.com \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox