Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: imre.deak@intel.com
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/dp: use EXPORT_SYMBOL_IF_KUNIT() for kunit helpers
Date: Wed, 16 Sep 2026 20:35:43 +0300	[thread overview]
Message-ID: <dd8d82c5ad95126fce1e42a2d9d7abb86a29fe57@intel.com> (raw)
In-Reply-To: <aqpg7Ci9a12a14dr@ideak-desk.lan>

On Wed, 16 Sep 2026, Imre Deak <imre.deak@intel.com> wrote:
> On Wed, Sep 16, 2026 at 10:27:52AM +0300, Jani Nikula wrote:
>> On Wed, 16 Sep 2026, Imre Deak <imre.deak@intel.com> wrote:
>> > On Tue, Sep 15, 2026 at 09:48:14PM +0300, Imre Deak wrote:
>> >> On Tue, Sep 15, 2026 at 07:06:20PM +0300, Jani Nikula wrote:
>> >> > Use EXPORT_SYMBOL_IF_KUNIT() instead of the regular EXPORT_SYMBOL() to
>> >> > export the symbols to the kunit namespace. Otherwise, the symbols get
>> >> > exported for all the kernel to see, and the corresponding
>> >> > MODULE_IMPORT_NS("EXPORTED_FOR_KUNIT_TESTING") in the tests is
>> >> > meaningless.
>> >> 
>> >> Yes, these symblols are only used by kunit, so no need to export them
>> >> otherwise. Should've thought about it while typing the above
>> >> MODULE_IMPORT_NS():
>> >> 
>> >> Reviewed-by: Imre Deak <imre.deak@intel.com>
>> >
>> > Actually, the symbols are defined and exported only if KUNIT is enabled
>> > without this patch already, as both of these are in an
>> > IS_ENABLED(CONFIG_KUNIT) block.
>> 
>> That only gates whether they're exported or not. The change is about
>> exporting them to the kunit namespace when they're exported.
>
> Right, so in a kunit build the visibility of symbols was still too
> broad. The R-b still applies.

Thanks, pushed!

BR,
Jani.

-- 
Jani Nikula, Intel

  reply	other threads:[~2026-09-16 17:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 16:06 [PATCH] drm/i915/dp: use EXPORT_SYMBOL_IF_KUNIT() for kunit helpers Jani Nikula
2026-09-15 18:48 ` Imre Deak
2026-09-16  4:51   ` Imre Deak
2026-09-16  7:27     ` Jani Nikula
2026-09-16  9:27       ` Imre Deak
2026-09-16 17:35         ` Jani Nikula [this message]
2026-09-15 19:52 ` ✓ i915.CI.BAT: success for " Patchwork
2026-09-16  6:12 ` ✓ i915.CI.Full: " Patchwork

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=dd8d82c5ad95126fce1e42a2d9d7abb86a29fe57@intel.com \
    --to=jani.nikula@intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.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