From: Petr Mladek <pmladek@suse.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
"Sergey Senozhatsky" <senozhatsky@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] vsprintf: Add test for restricted kernel pointers
Date: Thu, 14 May 2026 15:06:28 +0200 [thread overview]
Message-ID: <agXI1IYjwhyqISld@pathway.suse.cz> (raw)
In-Reply-To: <afh70XpLJD0RXPJu@ashevche-desk.local>
On Mon 2026-05-04 13:58:25, Andy Shevchenko wrote:
> On Mon, May 04, 2026 at 12:43:41PM +0200, Thomas Weißschuh wrote:
> > Fill out the tests for restricted kernel pointers, using the %pK format.
>
> ...
>
> > +#if IS_MODULE(CONFIG_PRINTF_KUNIT_TEST)
> > +EXPORT_SYMBOL_FOR_MODULES(kptr_restrict, "printf_kunit");
> > +#endif
>
> Same Q here.
Same here.
With the ifdeffs removed:
Reviewed-by: Petr Mladek <pmladek@suse.com>
Tested-by: Petr Mladek <pmladek@suse.com>
Best Regards,
Petr
PS: No need to send v3. I could remove the ifdeffs when committing
the patchset. I am going to commit it tomorrow unless anyone
complains.
I am sorry for the late review and short notice before committing.
I had vacation last 5 days. And I am traveling next week.
next prev parent reply other threads:[~2026-05-14 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 10:43 [PATCH v2 0/2] " Thomas Weißschuh
2026-05-04 10:43 ` [PATCH v2 1/2] vsprintf: Only export no_hash_pointers to test module Thomas Weißschuh
2026-05-04 10:57 ` Andy Shevchenko
2026-05-04 11:53 ` Thomas Weißschuh
2026-05-04 14:11 ` Andy Shevchenko
2026-05-14 11:58 ` Petr Mladek
2026-05-18 10:10 ` Thomas Weißschuh
2026-05-04 10:43 ` [PATCH v2 2/2] vsprintf: Add test for restricted kernel pointers Thomas Weißschuh
2026-05-04 10:58 ` Andy Shevchenko
2026-05-14 13:06 ` Petr Mladek [this message]
2026-05-21 14:18 ` [PATCH v2 0/2] " 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=agXI1IYjwhyqISld@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=thomas.weissschuh@linutronix.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
all inboxes | Powered by JetHome®