From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Raag Jadav" <raag.jadav@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ CI.checkpatch: warning for Introduce Xe PCIe FLR (rev6)
Date: Thu, 23 Apr 2026 10:09:22 -0000 [thread overview]
Message-ID: <177693896205.1681.748122813975143349@5ab824fced77> (raw)
In-Reply-To: <20260423100017.1051587-1-raag.jadav@intel.com>
== Series Details ==
Series: Introduce Xe PCIe FLR (rev6)
URL : https://patchwork.freedesktop.org/series/162055/
State : warning
== Summary ==
+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
1f57ba1afceae32108bd24770069f764d940a0e4
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 2f368e568876fa97bfa19f469b04c1101a97beb0
Author: Raag Jadav <raag.jadav@intel.com>
Date: Thu Apr 23 15:30:17 2026 +0530
drm/xe/pci: Introduce PCIe FLR
With bare minimum pieces in place, we can finally introduce PCIe Function
Level Reset (FLR) support which re-initializes hardware state without the
need for reloading the driver from userspace. All VRAM contents are lost
along with hardware state and driver takes care of recreating the required
kernel bos as part of re-initialization, but user still needs to recreate
user bos and reload context after PCIe FLR.
Signed-off-by: Raag Jadav <raag.jadav@intel.com>
Tested-by: Lukasz Laguna <lukasz.laguna@intel.com>
+ /mt/dim checkpatch 95fbbe4877e1543975d0d0f18a7cc0074416be41 drm-intel
f47498c70a1a drm/xe/uc_fw: Allow re-initializing firmware
2ad2176d4b05 drm/xe/guc_submit: Introduce guc_exec_queue_reinit()
f5366cfa6209 drm/xe/gt: Introduce FLR helpers
039a70cac294 drm/xe/bo_evict: Introduce xe_bo_restore_map()
52acedf63a26 drm/xe/exec_queue: Introduce xe_exec_queue_reinit()
0869e34577b6 drm/xe/migrate: Introduce xe_migrate_reinit()
0f2fc0bd4dc9 drm/xe/pm: Introduce xe_device_suspend/resume()
2f368e568876 drm/xe/pci: Introduce PCIe FLR
-:68: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#68:
new file mode 100644
-:119: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'xe_' - possible side-effects?
#119: FILE: drivers/gpu/drm/xe/xe_pci_error.c:47:
+#define XE_FLR_SKIP(xe_, pdev_) (!IS_DGFX(xe_) || IS_SRIOV_VF(xe_) || pci_num_vf(pdev_) || \
+ xe_->info.probe_display)
total: 0 errors, 1 warnings, 1 checks, 144 lines checked
next prev parent reply other threads:[~2026-04-23 10:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 10:00 [PATCH v6 0/8] Introduce Xe PCIe FLR Raag Jadav
2026-04-23 10:00 ` [PATCH v6 1/8] drm/xe/uc_fw: Allow re-initializing firmware Raag Jadav
2026-04-23 10:00 ` [PATCH v6 2/8] drm/xe/guc_submit: Introduce guc_exec_queue_reinit() Raag Jadav
2026-04-23 10:00 ` [PATCH v6 3/8] drm/xe/gt: Introduce FLR helpers Raag Jadav
2026-04-23 10:00 ` [PATCH v6 4/8] drm/xe/bo_evict: Introduce xe_bo_restore_map() Raag Jadav
2026-04-23 10:00 ` [PATCH v6 5/8] drm/xe/exec_queue: Introduce xe_exec_queue_reinit() Raag Jadav
2026-04-23 10:00 ` [PATCH v6 6/8] drm/xe/migrate: Introduce xe_migrate_reinit() Raag Jadav
2026-04-23 10:00 ` [PATCH v6 7/8] drm/xe/pm: Introduce xe_device_suspend/resume() Raag Jadav
2026-04-23 10:00 ` [PATCH v6 8/8] drm/xe/pci: Introduce PCIe FLR Raag Jadav
2026-04-28 23:28 ` Daniele Ceraolo Spurio
2026-04-29 4:33 ` Raag Jadav
2026-04-29 16:22 ` Rodrigo Vivi
2026-04-29 17:57 ` Daniele Ceraolo Spurio
2026-04-30 20:57 ` Rodrigo Vivi
2026-05-02 7:41 ` Raag Jadav
2026-05-08 10:53 ` Laguna, Lukasz
2026-04-23 10:09 ` Patchwork [this message]
2026-04-23 10:10 ` ✓ CI.KUnit: success for Introduce Xe PCIe FLR (rev6) Patchwork
2026-04-23 11:05 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-23 20:58 ` ✗ 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=177693896205.1681.748122813975143349@5ab824fced77 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=raag.jadav@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).