From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Lukasz Laguna" <lukasz.laguna@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ CI.checkpatch: warning for PF: Add support for MERT
Date: Fri, 31 Oct 2025 08:12:56 -0000 [thread overview]
Message-ID: <176189837617.3446.3167335806006871158@10055242dc62> (raw)
In-Reply-To: <20251031080501.844-1-lukasz.laguna@intel.com>
== Series Details ==
Series: PF: Add support for MERT
URL : https://patchwork.freedesktop.org/series/156807/
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
f867e605613af1770f90c4b0afd4a8f06424d1f0
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 2122e716bd4ce42cb14e8bb88b1abf4b1eda3018
Author: Lukasz Laguna <lukasz.laguna@intel.com>
Date: Fri Oct 31 09:05:01 2025 +0100
drm/xe/pf: Handle MERT catastrophic errors
The MERT block triggers an interrupt when a catastrophic error occurs.
Update the interrupt handler to read the MERT catastrophic error type
and log appropriate debug message.
Signed-off-by: Lukasz Laguna <lukasz.laguna@intel.com>
+ /mt/dim checkpatch fbd719e0eb058dd8b23a734e199f52e81cd9f267 drm-intel
2e7691cf79a5 drm/xe: Add device flag to indicate standalone MERT
d3cf577f9572 drm/xe/pf: Configure LMTT in MERT
-:12: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#12:
new file mode 100644
total: 0 errors, 1 warnings, 0 checks, 50 lines checked
c2de6d95825b drm/xe/pf: Add TLB invalidation support for MERT
-:139: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#139:
new file mode 100644
total: 0 errors, 1 warnings, 0 checks, 208 lines checked
2122e716bd4c drm/xe/pf: Handle MERT catastrophic errors
next prev parent reply other threads:[~2025-10-31 8:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 8:04 [PATCH v2 0/4] PF: Add support for MERT Lukasz Laguna
2025-10-31 8:04 ` [PATCH v2 1/4] drm/xe: Add device flag to indicate standalone MERT Lukasz Laguna
2025-10-31 8:04 ` [PATCH v2 2/4] drm/xe/pf: Configure LMTT in MERT Lukasz Laguna
2025-11-24 10:47 ` Piotr Piórkowski
2025-10-31 8:05 ` [PATCH v2 3/4] drm/xe/pf: Add TLB invalidation support for MERT Lukasz Laguna
2025-11-24 13:43 ` Piotr Piórkowski
2025-10-31 8:05 ` [PATCH v2 4/4] drm/xe/pf: Handle MERT catastrophic errors Lukasz Laguna
2025-11-24 13:52 ` Piotr Piórkowski
2025-10-31 8:12 ` Patchwork [this message]
2025-10-31 8:14 ` ✓ CI.KUnit: success for PF: Add support for MERT Patchwork
2025-10-31 9:29 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-31 19:25 ` ✓ Xe.CI.Full: " 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=176189837617.3446.3167335806006871158@10055242dc62 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lukasz.laguna@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