From: Kees Cook <kees@kernel.org>
To: Aditya Garg <gargaditya08@live.com>
Cc: "tamird@gmail.com" <tamird@gmail.com>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] printf: add tests for generic FourCCs
Date: Tue, 25 Mar 2025 12:48:57 -0700 [thread overview]
Message-ID: <202503251247.086BD45C@keescook> (raw)
In-Reply-To: <4378DDFE-3263-497A-8364-433DC1984FEE@live.com>
On Fri, Mar 14, 2025 at 03:45:01AM +0000, Aditya Garg wrote:
> From: Aditya Garg <gargaditya08@live.com>
>
> Format specifiers for printing generic 32-bit FourCCs were recently added
> to vsprintf. They are going through the DRM tree alongwith the appletbdrm
> driver. Since the printf tests are being converted to kunit, this separate
> patch for the tests should make it easier to rebase when the merge window
> opens.
>
> Link: https://lore.kernel.org/dri-devel/79FA3F41-FD7A-41D9-852B-D32606AF5EB4@live.com/T/#u
> Signed-off-by: Aditya Garg <gargaditya08@live.com>
> ---
> lib/tests/printf_kunit.c | 39 ++++++++++++++++++++++++++++++++-------
Linus has applied the kunit /lib move tree, so this patch can land via
regular trees now. Who should take it?
--
Kees Cook
next prev parent reply other threads:[~2025-03-25 19:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 3:45 [PATCH] printf: add tests for generic FourCCs Aditya Garg
2025-03-21 14:10 ` Andy Shevchenko
2025-03-21 14:16 ` Tamir Duberstein
2025-03-21 14:23 ` Aditya Garg
2025-03-21 14:52 ` Tamir Duberstein
2025-03-22 10:04 ` Aditya Garg
2025-03-22 13:30 ` Tamir Duberstein
2025-03-25 19:48 ` Kees Cook [this message]
2025-03-26 0:26 ` Aditya Garg
2025-03-27 9:57 ` Petr Mladek
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=202503251247.086BD45C@keescook \
--to=kees@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gargaditya08@live.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tamird@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.