Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Sobin Thomas" <sobin.thomas@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ CI.checkpatch: success for series starting with [i-g-t,1/1] drm/xe: xe_hw_engine_class: Add fault injection and improve error handling in kobj_xe_hw_engine_class (rev2)
Date: Mon, 07 Apr 2025 13:25:56 -0000	[thread overview]
Message-ID: <174403235628.43425.3816277705857142964@e6b6f09ec485> (raw)
In-Reply-To: <20250405065432.2254703-1-sobin.thomas@intel.com>

== Series Details ==

Series: series starting with [i-g-t,1/1] drm/xe: xe_hw_engine_class: Add fault injection and improve error handling in kobj_xe_hw_engine_class (rev2)
URL   : https://patchwork.freedesktop.org/series/147289/
State : success

== 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
99e5a866b5e13f134e606a3e29d9508d97826fb3
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 0c54e4b0b9c3620e16bea622609afee74e817d58
Author: Sobin Thomas <sobin.thomas@intel.com>
Date:   Sat Apr 5 06:54:32 2025 +0000

    drm/xe: xe_hw_engine_class: Add fault injection and improve error handling in kobj_xe_hw_engine_class
    
    - Added fault injection for `kobj_xe_hw_engine_class` to enhance coverage.
    - Improved error handling by checking for `IS_ERR_OR_NULL` on `keclass` and
      propagating the error using `PTR_ERR`.
    
    Can be tested using inject-fault-probe-function-kobj_xe_hw_engine_class
    
    Signed-off-by: Sobin Thomas <sobin.thomas@intel.com>
+ /mt/dim checkpatch 5bb36322dc543ec6a0e7389b6735f174dc203fa5 drm-intel
0c54e4b0b9c3 drm/xe: xe_hw_engine_class: Add fault injection and improve error handling in kobj_xe_hw_engine_class



  parent reply	other threads:[~2025-04-07 13:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-05  6:54 [PATCH i-g-t 1/1] drm/xe: xe_hw_engine_class: Add fault injection and improve error handling in kobj_xe_hw_engine_class Sobin Thomas
2025-04-05  7:14 ` ✓ CI.Patch_applied: success for series starting with [i-g-t,1/1] " Patchwork
2025-04-05  7:15 ` ✓ CI.checkpatch: " Patchwork
2025-04-05  7:16 ` ✓ CI.KUnit: " Patchwork
2025-04-05  7:32 ` ✓ CI.Build: " Patchwork
2025-04-05  7:35 ` ✓ CI.Hooks: " Patchwork
2025-04-05  7:36 ` ✓ CI.checksparse: " Patchwork
2025-04-07  3:30 ` [PATCH i-g-t 1/1] " Upadhyay, Tejas
2025-04-07 13:25 ` ✓ CI.Patch_applied: success for series starting with [i-g-t,1/1] drm/xe: xe_hw_engine_class: Add fault injection and improve error handling in kobj_xe_hw_engine_class (rev2) Patchwork
2025-04-07 13:25 ` Patchwork [this message]
2025-04-07 13:27 ` ✓ CI.KUnit: " Patchwork
2025-04-07 13:30 ` ✗ CI.Build: failure " Patchwork
2025-04-07 20:13 ` ✓ Xe.CI.Full: success for series starting with [i-g-t,1/1] drm/xe: xe_hw_engine_class: Add fault injection and improve error handling in kobj_xe_hw_engine_class 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=174403235628.43425.3816277705857142964@e6b6f09ec485 \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=sobin.thomas@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