From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Soham Purkait" <soham.purkait@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ CI.checkpatch: warning for drm/xe: Add support for GPU health indicator
Date: Thu, 23 Apr 2026 17:52:53 -0000 [thread overview]
Message-ID: <177696677301.2765.6797465974830859008@5ab824fced77> (raw)
In-Reply-To: <20260423173925.699486-1-soham.purkait@intel.com>
== Series Details ==
Series: drm/xe: Add support for GPU health indicator
URL : https://patchwork.freedesktop.org/series/165378/
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 ff1507e8976895a1688ab1f49b2bfc0fa3782b39
Author: Soham Purkait <soham.purkait@intel.com>
Date: Thu Apr 23 23:09:25 2026 +0530
drm/xe/xe_ras: Add RAS support for GPU health indicator
GPU health indicator exposes a single sysfs interface, gpu_health,
at the device level, allowing administrators and management tools to
query the GPU health status. The interface permits both read and write
operations on PF and native functions, while on VFs it is exposed as
read-only.
The sysfs file (gpu_health) is placed at the device level and behaves as
follows:
$ cat /sys/.../device/gpu_health
ok
$ echo critical > /sys/.../device/gpu_health
$ cat /sys/.../device/gpu_health
critical
V2:
- Return error number instead of error message in _show and
_store. (Andi)
- Remove redundant VF check in _store callback. (Andi)
- Move GPU health sysfs init error logging to xe_ras_init. (Andi)
- Return only the current health state for sysfs read. (Andi, Rodrigo)
- Add documentation for sysfs interface. (Andi, Rodrigo)
Signed-off-by: Soham Purkait <soham.purkait@intel.com>
+ /mt/dim checkpatch ecb61ba4a1f619b6944f4d0741b4d8a0910f460c drm-intel
97583930f1c3 drm/xe/xe_ras: Add types and commands for RAS GPU health indicator
-:30: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#30:
new file mode 100644
total: 0 errors, 1 warnings, 0 checks, 104 lines checked
ff1507e89768 drm/xe/xe_ras: Add RAS support for GPU health indicator
-:34: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#34:
new file mode 100644
total: 0 errors, 1 warnings, 0 checks, 270 lines checked
next prev parent reply other threads:[~2026-04-23 17:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 17:39 [PATCH v2 0/2] drm/xe: Add support for GPU health indicator Soham Purkait
2026-04-23 17:39 ` [PATCH v2 1/2] drm/xe/xe_ras: Add types and commands for RAS " Soham Purkait
2026-04-28 8:56 ` Tauro, Riana
2026-04-29 5:24 ` Purkait, Soham
2026-04-29 5:34 ` Raag Jadav
2026-04-28 13:19 ` Andi Shyti
2026-04-23 17:39 ` [PATCH v2 2/2] drm/xe/xe_ras: Add RAS support for " Soham Purkait
2026-04-27 22:16 ` Rodrigo Vivi
2026-04-28 8:24 ` Tauro, Riana
2026-04-28 12:57 ` Andi Shyti
2026-04-29 6:07 ` Purkait, Soham
2026-04-28 13:47 ` Andi Shyti
2026-04-29 5:39 ` Raag Jadav
2026-04-23 17:52 ` Patchwork [this message]
2026-04-23 17:54 ` ✓ CI.KUnit: success for drm/xe: Add " Patchwork
2026-04-23 19:02 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-24 2:52 ` ✓ Xe.CI.FULL: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2026-07-10 8:33 [PATCH v10 0/1] " Soham Purkait
2026-07-10 9:20 ` ✗ CI.checkpatch: warning for " Patchwork
2026-07-10 4:15 [PATCH v9 0/1] " Soham Purkait
2026-07-10 4:22 ` ✗ CI.checkpatch: warning for " Patchwork
2026-07-08 13:51 [PATCH v8 0/1] " Soham Purkait
2026-07-08 13:59 ` ✗ CI.checkpatch: warning for " Patchwork
2026-07-08 6:12 [PATCH v7 0/1] " Soham Purkait
2026-07-08 6:18 ` ✗ CI.checkpatch: warning for " Patchwork
2026-07-06 16:52 [PATCH v6 0/1] " Soham Purkait
2026-07-06 16:59 ` ✗ CI.checkpatch: warning for " Patchwork
2026-06-18 6:10 [PATCH v5 0/1] " Soham Purkait
2026-06-18 6:52 ` ✗ CI.checkpatch: warning for " Patchwork
2026-06-10 9:33 [PATCH v4 0/1] " Soham Purkait
2026-06-10 9:39 ` ✗ CI.checkpatch: warning for " Patchwork
2026-06-08 5:25 [PATCH v3 0/3] " Soham Purkait
2026-06-08 5:31 ` ✗ CI.checkpatch: warning for " Patchwork
2026-04-16 9:36 [PATCH v1 0/2] " Soham Purkait
2026-04-16 9:55 ` ✗ CI.checkpatch: warning for " Patchwork
2026-03-09 5:17 [PATCH 0/3] " Soham Purkait
2026-03-09 5:28 ` ✗ CI.checkpatch: warning 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=177696677301.2765.6797465974830859008@5ab824fced77 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=soham.purkait@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).