From: Jani Nikula <jani.nikula@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
Riana Tauro <riana.tauro@intel.com>
Cc: intel-xe@lists.freedesktop.org, anshuman.gupta@intel.com,
matthew.d.roper@intel.com
Subject: Re: [PATCH] drm/xe: select CONFIGFS_FS dependency
Date: Mon, 22 Dec 2025 14:42:05 +0200 [thread overview]
Message-ID: <a4928fe2e89de39161f8b794e798998a3fbebdd1@intel.com> (raw)
In-Reply-To: <aUV3dk3wUpf7U6tP@intel.com>
On Fri, 19 Dec 2025, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> On Fri, Dec 19, 2025 at 01:35:14PM +0530, Riana Tauro wrote:
>> Xe driver uses configfs functions to expose configuration to userspace.
>> If CONFIGFS_FS is built as module (=m) when Xe is built-in (=y),
>> undefined reference errors occur.
>
> Perhaps we don't need this middle phrase. Only the first and the last.
> But anyway, we need the patch in. I just pushed it.
I think the correct fix to this one would've been
depends on CONFIGFS_FS || CONFIGFS_FS=n
BR,
Jani.
>
> Thanks,
> Rodrigo.
>
>> Add select CONFIGFS_FS to ensure configfs is built at minimum required
>> level.
>>
>> Cc: Matt Roper <matthew.d.roper@intel.com>
>> Reported-by: kernel test robot <lkp@intel.com>
>> Closes: https://lore.kernel.org/oe-kbuild-all/202512190827.IeXYj4qg-lkp@intel.com/
>> Closes: https://lore.kernel.org/oe-kbuild-all/202512181854.hPyTAXc5-lkp@intel.com/
>> Closes: https://lore.kernel.org/oe-kbuild-all/202512190407.CcUFXX2F-lkp@intel.com/
>> Fixes: 16280ded45fb ("drm/xe: Add configfs to enable survivability mode")
>> Signed-off-by: Riana Tauro <riana.tauro@intel.com>
>> ---
>> drivers/gpu/drm/xe/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/gpu/drm/xe/Kconfig b/drivers/gpu/drm/xe/Kconfig
>> index 4b288eb3f5b0..1094c5fc5bdf 100644
>> --- a/drivers/gpu/drm/xe/Kconfig
>> +++ b/drivers/gpu/drm/xe/Kconfig
>> @@ -46,6 +46,7 @@ config DRM_XE
>> select WANT_DEV_COREDUMP
>> select AUXILIARY_BUS
>> select REGMAP if I2C
>> + select CONFIGFS_FS
>> help
>> Driver for Intel Xe2 series GPUs and later. Experimental support
>> for Xe series is also available.
>> --
>> 2.47.1
>>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-12-22 12:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 8:05 [PATCH] drm/xe: select CONFIGFS_FS dependency Riana Tauro
2025-12-19 8:26 ` ✓ CI.KUnit: success for " Patchwork
2025-12-19 9:00 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-19 16:04 ` [PATCH] " Rodrigo Vivi
2025-12-19 16:32 ` Matt Roper
2025-12-19 16:42 ` Michal Wajdeczko
2025-12-19 16:53 ` Matt Roper
2025-12-19 17:00 ` Vivi, Rodrigo
2025-12-21 10:48 ` Riana Tauro
2025-12-22 15:10 ` Rodrigo Vivi
2025-12-22 12:42 ` Jani Nikula [this message]
2026-01-02 14:57 ` Riana Tauro
2026-01-02 15:13 ` Jani Nikula
2025-12-20 10:07 ` ✗ Xe.CI.Full: failure for " 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=a4928fe2e89de39161f8b794e798998a3fbebdd1@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=riana.tauro@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox