From: Jani Nikula <jani.nikula@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>, intel-xe@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
kernel test robot <lkp@intel.com>,
Matt Roper <matthew.d.roper@intel.com>
Subject: Re: [PATCH] drm/xe: Fix build with DRM_XE=y and CONFIGFS_FS=m
Date: Mon, 19 Oct 2026 18:21:29 +0300 [thread overview]
Message-ID: <9411b525240f8b79c2d828a887d1679518374689@intel.com> (raw)
In-Reply-To: <20261016193254.3042071-2-rodrigo.vivi@intel.com>
On Fri, 16 Oct 2026, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> When xe is built-in but configfs is a module, xe_configfs.o is not
> linked into xe, while IS_ENABLED(CONFIG_CONFIGFS_FS) in xe_configfs.h
> still exposes the real declarations, leading to undefined references.
>
> Use IS_REACHABLE() so this case falls back to the stubs, the same as
> CONFIGFS_FS=n.
I think using IS_REACHABLE() is almost always a mistake. It's a hack to
avoid link errors when something in a module needs something that is
built-in. It's a combo that should be handled at Kconfig level, not at
build level.
BR,
Jani.
>
> Fixes: 16280ded45fb ("drm/xe: Add configfs to enable survivability mode")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202610160935.Qk4ZxBxY-lkp@intel.com/
> Suggested-by: Matt Roper <matthew.d.roper@intel.com>
> Assisted-by: LLM
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/xe/xe_configfs.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_configfs.h b/drivers/gpu/drm/xe/xe_configfs.h
> index 10a00d6bbf8f..327b648944ff 100644
> --- a/drivers/gpu/drm/xe/xe_configfs.h
> +++ b/drivers/gpu/drm/xe/xe_configfs.h
> @@ -14,7 +14,7 @@
>
> struct pci_dev;
>
> -#if IS_ENABLED(CONFIG_CONFIGFS_FS)
> +#if IS_REACHABLE(CONFIG_CONFIGFS_FS)
> int xe_configfs_init(void);
> void xe_configfs_exit(void);
> void xe_configfs_check_device(struct pci_dev *pdev);
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-10-19 15:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 17:29 [PATCH] drm/xe: Fix build with DRM_XE=y and CONFIGFS_FS=m Rodrigo Vivi
2026-10-16 17:39 ` ✓ CI.KUnit: success for " Patchwork
2026-10-16 18:20 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-16 18:54 ` [PATCH] " Summers, Stuart
2026-10-16 19:18 ` Matt Roper
2026-10-16 19:32 ` Rodrigo Vivi
2026-10-19 15:21 ` Jani Nikula [this message]
2026-10-19 15:25 ` Matt Roper
2026-10-19 16:53 ` Jani Nikula
2026-10-19 17:06 ` Matt Roper
2026-10-19 21:58 ` Rodrigo Vivi
2026-10-19 22:55 ` Matt Roper
2026-10-16 19:44 ` ✓ CI.KUnit: success for drm/xe: Fix build with DRM_XE=y and CONFIGFS_FS=m (rev2) Patchwork
2026-10-16 20:25 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-17 2:10 ` ✓ Xe.CI.FULL: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2026-10-21 19:45 [PATCH] drm/xe: Fix build with DRM_XE=y and CONFIGFS_FS=m Rodrigo Vivi
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=9411b525240f8b79c2d828a887d1679518374689@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lkp@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=rodrigo.vivi@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.