mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Tamir Duberstein <tamird@kernel.org>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v1 1/1] lib/vsprintf: Use EXPORT_SYMBOL_IF_KUNIT() to export symbols
Date: Wed, 14 Oct 2026 11:34:45 +0200	[thread overview]
Message-ID: <as9MtfUWfFqHp1YB@pathway.suse.cz> (raw)
In-Reply-To: <as6XcMDhDGoCHYP0@ashevche-desk.local>

On Tue 2026-10-13 23:41:20, Andy Shevchenko wrote:
> On Tue, Jul 14, 2026 at 03:39:23PM +0100, Tamir Duberstein wrote:
> > On Tue, Jul 14, 2026 at 5:21 AM Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> > >
> > > Replace EXPORT_SYMBOL_FOR_MODULES() with EXPORT_SYMBOL_IF_KUNIT()
> > > to mark the symbols as visible only if CONFIG_KUNIT is enabled.
> > >
> > > Kunit test should import the namespace EXPORTED_FOR_KUNIT_TESTING to
> > > use these marked symbols. This is the standard way for all KUnit
> > > tests.
> > >
> > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > 
> > Acked-by: Tamir Duberstein <tamird@kernel.org>
> 
> Thanks!
> 
> Petr, does this fall in cracks? Can it be applied or do you have any comments
> on this? Or may be I missed something?

Yeah, this has fallen through the cracks. /o\

I have just committed it into printk/linux.git, branch for-7.4.

Thanks a lot for reminder.

Best Regards,
Petr

      reply	other threads:[~2026-10-14  9:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 12:21 Andy Shevchenko
2026-07-14 14:39 ` Tamir Duberstein
2026-10-13 20:41   ` Andy Shevchenko
2026-10-14  9:34     ` 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=as9MtfUWfFqHp1YB@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=tamird@kernel.org \
    /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®