From: Kees Cook <kees@kernel.org>
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" <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>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"apw@canonical.com" <apw@canonical.com>,
"joe@perches.com" <joe@perches.com>,
"dwaipayanray1@gmail.com" <dwaipayanray1@gmail.com>,
"lukas.bulwahn@gmail.com" <lukas.bulwahn@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Hector Martin <marcan@marcan.st>,
"asahi@lists.linux.dev" <asahi@lists.linux.dev>
Subject: Re: [PATCH 1/2] lib/vsprintf: Add support for generic FourCCs by extending %p4cc
Date: Thu, 13 Mar 2025 17:05:32 -0700 [thread overview]
Message-ID: <0F278A68-EC62-4267-9AC0-C1FFB9B5592E@kernel.org> (raw)
In-Reply-To: <PN3PR01MB95972EFA147FB0453D5A7FABB8D32@PN3PR01MB9597.INDPRD01.PROD.OUTLOOK.COM>
On March 13, 2025 10:42:10 AM PDT, Aditya Garg <gargaditya08@live.com> wrote:
>I already sent the 1st patch to DRM. I can rebase the test-printf bit to this tree. Sounds good?
Yeah, sounds good to me! Thanks :)
-Kees
--
Kees Cook
next prev parent reply other threads:[~2025-03-14 0:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 9:04 [PATCH 0/2] Use proper printk format in appletbdrm Aditya Garg
2025-03-12 9:05 ` [PATCH 1/2] lib/vsprintf: Add support for generic FourCCs by extending %p4cc Aditya Garg
2025-03-12 11:46 ` Thomas Zimmermann
2025-03-12 11:49 ` Aditya Garg
2025-03-12 11:58 ` Thomas Zimmermann
2025-03-12 12:03 ` Aditya Garg
2025-03-12 12:07 ` Aditya Garg
2025-03-12 15:34 ` Sven Peter
2025-03-12 19:14 ` Aditya Garg
2025-03-12 19:28 ` Andy Shevchenko
2025-03-12 19:35 ` Aditya Garg
2025-03-12 19:51 ` Andy Shevchenko
2025-03-13 7:26 ` Aditya Garg
2025-03-13 8:48 ` Andy Shevchenko
2025-03-13 8:53 ` Aditya Garg
2025-03-13 8:56 ` Andy Shevchenko
2025-03-13 9:13 ` Aditya Garg
2025-03-13 10:48 ` Petr Mladek
2025-03-13 11:06 ` Aditya Garg
2025-03-13 13:24 ` Andy Shevchenko
2025-03-13 17:40 ` Kees Cook
2025-03-13 17:42 ` Aditya Garg
2025-03-14 0:05 ` Kees Cook [this message]
2025-03-12 9:06 ` [PATCH 2/2] drm/appletbdm: use %p4cl instead of %p4cc Aditya Garg
2025-03-12 11:51 ` Thomas Zimmermann
2025-03-12 14:51 ` andriy.shevchenko
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=0F278A68-EC62-4267-9AC0-C1FFB9B5592E@kernel.org \
--to=kees@kernel.org \
--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=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=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