From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Badal Nilawar <badal.nilawar@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<anshuman.gupta@intel.com>, <alexander.usyskin@intel.com>,
<gregkh@linuxfoundation.org>, <daniele.ceraolospurio@intel.com>
Subject: Re: [PATCH v5 10/10] drm/xe/xe_late_bind_fw: Select INTEL_MEI_LATE_BIND for CI
Date: Wed, 2 Jul 2025 17:48:13 -0400 [thread overview]
Message-ID: <aGWpHRrPR39LWKQ1@intel.com> (raw)
In-Reply-To: <20250702165216.557074-11-badal.nilawar@intel.com>
On Wed, Jul 02, 2025 at 10:22:16PM +0530, Badal Nilawar wrote:
> Do not review
Why?
Why don't we add this dependency here?
>
> Signed-off-by: Badal Nilawar <badal.nilawar@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 f66e6d39e319..ef3f4807b0b3 100644
> --- a/drivers/gpu/drm/xe/Kconfig
> +++ b/drivers/gpu/drm/xe/Kconfig
> @@ -45,6 +45,7 @@ config DRM_XE
> select WANT_DEV_COREDUMP
> select AUXILIARY_BUS
> select HMM_MIRROR
> + select INTEL_MEI_LATE_BIND
> help
> Driver for Intel Xe2 series GPUs and later. Experimental support
> for Xe series is also available.
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-07-02 21:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 16:52 [PATCH v5 00/10] Introducing firmware late binding Badal Nilawar
2025-07-02 16:52 ` [PATCH v5 01/10] mei: bus: add mei_cldev_mtu interface Badal Nilawar
2025-07-02 16:52 ` [PATCH v5 02/10] mei: late_bind: add late binding component driver Badal Nilawar
2025-07-02 16:52 ` [PATCH v5 03/10] drm/xe/xe_late_bind_fw: Introducing xe_late_bind_fw Badal Nilawar
2025-07-02 16:52 ` [PATCH v5 04/10] drm/xe/xe_late_bind_fw: Initialize late binding firmware Badal Nilawar
2025-07-02 23:55 ` Daniele Ceraolo Spurio
2025-07-02 16:52 ` [PATCH v5 05/10] drm/xe/xe_late_bind_fw: Load " Badal Nilawar
2025-07-02 16:52 ` [PATCH v5 06/10] drm/xe/xe_late_bind_fw: Reload late binding fw in rpm resume Badal Nilawar
2025-07-02 21:46 ` Rodrigo Vivi
2025-07-02 16:52 ` [PATCH v5 07/10] drm/xe/xe_late_bind_fw: Reload late binding fw during system resume Badal Nilawar
2025-07-02 21:46 ` Rodrigo Vivi
2025-07-02 16:52 ` [PATCH v5 08/10] drm/xe/xe_late_bind_fw: Introduce debug fs node to disable late binding Badal Nilawar
2025-07-03 0:12 ` Daniele Ceraolo Spurio
2025-07-02 16:52 ` [PATCH v5 09/10] drm/xe/xe_late_bind_fw: Extract and print version info Badal Nilawar
2025-07-02 16:52 ` [PATCH v5 10/10] drm/xe/xe_late_bind_fw: Select INTEL_MEI_LATE_BIND for CI Badal Nilawar
2025-07-02 21:48 ` Rodrigo Vivi [this message]
2025-07-03 17:06 ` Daniele Ceraolo Spurio
2025-07-02 18:39 ` ✗ CI.checkpatch: warning for Introducing firmware late binding Patchwork
2025-07-02 18:40 ` ✓ CI.KUnit: success " Patchwork
2025-07-02 18:58 ` ✗ CI.checksparse: warning " Patchwork
2025-07-02 19:40 ` ✓ Xe.CI.BAT: success " Patchwork
2025-07-04 11:03 ` ✗ Xe.CI.Full: failure " 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=aGWpHRrPR39LWKQ1@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).