Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Riana Tauro <riana.tauro@intel.com>,
	<intel-xe@lists.freedesktop.org>, <anshuman.gupta@intel.com>
Subject: Re: [PATCH] drm/xe: select CONFIGFS_FS dependency
Date: Fri, 19 Dec 2025 17:42:36 +0100	[thread overview]
Message-ID: <43529e9d-3bd4-44d5-a603-8394a7a0f049@intel.com> (raw)
In-Reply-To: <20251219163238.GN4164497@mdroper-desk1.amr.corp.intel.com>



On 12/19/2025 5:32 PM, Matt Roper wrote:
> On Fri, Dec 19, 2025 at 11:04:06AM -0500, Rodrigo Vivi 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.
>>
>> Thanks,
>> Rodrigo.
>>
>>> Add select CONFIGFS_FS to ensure configfs is built at minimum required
>>> level.
> 
> If we make this change, shouldn't we also remove all of the #ifdef logic
> we have to support running without configfs?

but is it a good idea to always back select CONFIGFS ?
maybe the actual fix should be like this:

-xe-$(CONFIG_CONFIGFS_FS) += xe_configfs.o
+
+ifdef CONFIG_CONFIGFS_FS
+       xe-y += xe_configfs.o
+endif


> 
> 
> Matt
> 
>>>
>>> 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
>>>
> 


  reply	other threads:[~2025-12-19 16: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 [this message]
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
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=43529e9d-3bd4-44d5-a603-8394a7a0f049@intel.com \
    --to=michal.wajdeczko@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