From: Gabriele Paoloni <gpaoloni@redhat.com>
To: corbet@lwn.net, skhan@linuxfoundation.org, arnd@arndb.de,
gregkh@linuxfoundation.org, brendan.higgins@linux.dev,
raemoar63@gmail.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
kunit-dev@googlegroups.com
Cc: acarminati@nvidia.com, linux-mm@kvack.org,
safety-architecture@lists.elisa.tech,
kstewart@linuxfoundation.org, chuckwolber@gmail.com,
gpaoloni@redhat.com, Alessandro Carminati <acarmina@redhat.com>
Subject: [RFC PATCH v3 3/6] kunit: add visibility helpers for static inline functions
Date: Thu, 12 Feb 2026 13:49:20 +0100 [thread overview]
Message-ID: <20260212124923.222484-4-gpaoloni@redhat.com> (raw)
In-Reply-To: <20260212124923.222484-1-gpaoloni@redhat.com>
From: Alessandro Carminati <acarmina@redhat.com>
Add KUnit visibility helpers for static inline functions so they can be
referenced by test code when KUnit is enabled.
This change does not alter behavior or expose new functionality at
runtime; it only provides a mechanism to override visibility for
testing purposes.
Signed-off-by: Alessandro Carminati <acarmina@redhat.com>
---
include/kunit/visibility.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/kunit/visibility.h b/include/kunit/visibility.h
index 7c34c8ffcf3b..82ab7fffc943 100644
--- a/include/kunit/visibility.h
+++ b/include/kunit/visibility.h
@@ -17,6 +17,7 @@
* there is no change to the symbol definition.
*/
#define VISIBLE_IF_KUNIT
+ #define INLINE_VISIBLE_IF_KUNIT
/**
* EXPORT_SYMBOL_IF_KUNIT(symbol) - Exports symbol into
* EXPORTED_FOR_KUNIT_TESTING namespace only if CONFIG_KUNIT is
@@ -27,6 +28,7 @@
#define EXPORT_SYMBOL_IF_KUNIT(symbol) EXPORT_SYMBOL_NS(symbol, "EXPORTED_FOR_KUNIT_TESTING")
#else
#define VISIBLE_IF_KUNIT static
+ #define INLINE_VISIBLE_IF_KUNIT static inline
#define EXPORT_SYMBOL_IF_KUNIT(symbol)
#endif
--
2.48.1
next prev parent reply other threads:[~2026-02-12 12:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 12:49 [RFC PATCH v3 0/6] some /dev/mem specifications and traced testing Gabriele Paoloni
2026-02-12 12:49 ` [RFC PATCH v3 1/6] Documentation: extend the 'Function documentation' with expected behavior and constraints of use Gabriele Paoloni
2026-02-12 12:59 ` Greg KH
2026-02-12 14:00 ` Gabriele Paoloni
2026-02-12 15:23 ` Greg KH
2026-02-13 17:13 ` Gabriele Paoloni
2026-02-12 12:49 ` [RFC PATCH v3 2/6] /dev/mem: Add initial documentation of memory_open() and mem_fops Gabriele Paoloni
2026-02-12 12:49 ` Gabriele Paoloni [this message]
2026-02-12 12:49 ` [RFC PATCH v3 4/6] char: mem: expose devmem helpers for KUnit testing Gabriele Paoloni
2026-02-12 12:49 ` [RFC PATCH v3 5/6] char: mem: add KUnit tests for /dev/mem read_mem() Gabriele Paoloni
2026-02-12 12:49 ` [RFC PATCH v3 6/6] char: mem: add Kconfig option for devmem KUnit tests Gabriele Paoloni
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=20260212124923.222484-4-gpaoloni@redhat.com \
--to=gpaoloni@redhat.com \
--cc=acarmina@redhat.com \
--cc=acarminati@nvidia.com \
--cc=arnd@arndb.de \
--cc=brendan.higgins@linux.dev \
--cc=chuckwolber@gmail.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=raemoar63@gmail.com \
--cc=safety-architecture@lists.elisa.tech \
--cc=skhan@linuxfoundation.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