[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <174864052958.2498160.13310755033812764996.b4-ty@intel.com>
Date: Fri, 30 May 2025 14:29:26 -0700
From: Lucas De Marchi <lucas.demarchi@...el.com>
To: intel-xe@...ts.freedesktop.org,
Lucas De Marchi <lucas.demarchi@...el.com>
Cc: Arnd Bergmann <arnd@...db.de>,
Arnd Bergmann <arnd@...nel.org>,
Thomas Hellström <thomas.hellstrom@...ux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@...el.com>,
Dave Airlie <airlied@...il.com>,
Simona Vetter <simona@...ll.ch>,
Matthew Brost <matthew.brost@...el.com>,
Himal Prasad Ghimiray <himal.prasad.ghimiray@...el.com>,
Imre Deak <imre.deak@...el.com>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
"Michael J. Ruhl" <michael.j.ruhl@...el.com>,
dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org,
dri-devel <dri-devel-bounces@...ts.freedesktop.org>
Subject: Re: [PATCH v2] drm/xe/vsec: fix CONFIG_INTEL_VSEC dependency
On Thu, 29 May 2025 10:23:56 -0700, Lucas De Marchi wrote:
> The XE driver can be built with or without VSEC support, but fails to link as
> built-in if vsec is in a loadable module:
>
> x86_64-linux-ld: vmlinux.o: in function `xe_vsec_init':
> (.text+0x1e83e16): undefined reference to `intel_vsec_register'
>
> The normal fix for this is to add a 'depends on INTEL_VSEC || !INTEL_VSEC',
> forcing XE to be a loadable module as well, but that causes a circular
> dependency:
>
> [...]
Applied to drm-xe-next, thanks!
[1/1] drm/xe/vsec: fix CONFIG_INTEL_VSEC dependency
commit: e4931f8be347ec5f19df4d6d33aea37145378c42
Best regards,
--
Lucas De Marchi
Powered by blists - more mailing lists