From: Petr Mladek <pmladek@suse.com>
To: Aditya Garg <gargaditya08@live.com>
Cc: Kees Cook <kees@kernel.org>,
"tamird@gmail.com" <tamird@gmail.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: Thu, 27 Mar 2025 10:57:04 +0100 [thread overview]
Message-ID: <Z-Ug8FeyJ9fTMhNf@pathway.suse.cz> (raw)
In-Reply-To: <PN0PR01MB958842137184723FD29694E7B8A62@PN0PR01MB9588.INDPRD01.PROD.OUTLOOK.COM>
On Wed 2025-03-26 00:26:08, Aditya Garg wrote:
>
>
> > On 26 Mar 2025, at 1:19 AM, Kees Cook <kees@kernel.org> wrote:
> >
> > 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?
>
> For some reason DRM has not taken up the patch set yet, even after approvals.
> I assume it's partly because gitlab.freedesktop.org was down for a whole week.
> Now that merge window is open, I myself dunno what is gonna happen with those patches.
> Also, I doubt DRM wants to take this up later. So, I have 2 options:
>
> 1. Just wait a bit more, probably till merge window settles so that DRM can take up those patches and then you take this one up.
> 2. I'll just send you the non DRM patch, and upstream it via you so that atleast you can get free. Then. I'll tell DRM to just upstream the DRM relevant patch, again after merge windows settles. The patch is anyways a bug fix, rather than something new.
I prefer the first solution. I'll take this patch after the already
queued patches reach the mainline.
Best Regards,
Petr
prev parent reply other threads:[~2025-03-27 9:57 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
2025-03-26 0:26 ` Aditya Garg
2025-03-27 9:57 ` Petr Mladek [this message]
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=Z-Ug8FeyJ9fTMhNf@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gargaditya08@live.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox