Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shuicheng Lin <shuicheng.lin@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Shuicheng Lin <shuicheng.lin@intel.com>
Subject: [PATCH 0/2] Remove unused code in devcoredump_snapshot
Date: Thu,  3 Jul 2025 06:20:25 +0000	[thread overview]
Message-ID: <20250703062024.3441918-4-shuicheng.lin@intel.com> (raw)

Remove unused code in devcoredump_snapshot().
Release runtime pm for error path of xe_devcoredump_read()

Shuicheng Lin (2):
  drm/xe: Remove unused code in devcoredump_snapshot()
  drm/xe: Release runtime pm for error path of xe_devcoredump_read()

 drivers/gpu/drm/xe/xe_devcoredump.c | 44 +++++++++++++++++------------
 1 file changed, 26 insertions(+), 18 deletions(-)

-- 
2.49.0


             reply	other threads:[~2025-07-03  6:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03  6:20 Shuicheng Lin [this message]
2025-07-03  6:20 ` [PATCH 1/2] drm/xe: Remove unused code in devcoredump_snapshot() Shuicheng Lin
2025-07-03  6:20 ` [PATCH 2/2] drm/xe: Release runtime pm for error path of xe_devcoredump_read() Shuicheng Lin
2025-07-03  6:57   ` Matthew Brost
2025-07-03  7:01   ` Matthew Brost
2025-07-03  6:29 ` ✗ CI.checkpatch: warning for Remove unused code in devcoredump_snapshot Patchwork
2025-07-03  6:30 ` ✓ CI.KUnit: success " Patchwork
2025-07-03  7:41 ` [PATCH v2 0/2] Remove unused code in devcoredump_snapshot() Shuicheng Lin
2025-07-03  7:41   ` [PATCH v2 1/2] drm/xe: " Shuicheng Lin
2025-07-03 14:38     ` Dong, Zhanjun
2025-07-03 15:35     ` Matthew Brost
2025-07-03  7:41   ` [PATCH v2 2/2] drm/xe: Release runtime pm for error path of xe_devcoredump_read() Shuicheng Lin
2025-07-03 15:34     ` Matthew Brost
2025-07-04  5:56 ` ✗ CI.checkpatch: warning for Remove unused code in devcoredump_snapshot (rev2) Patchwork
2025-07-04  5:57 ` ✓ CI.KUnit: success " Patchwork
2025-07-04 20:01 ` ✗ Xe.CI.Full: failure for Remove unused code in devcoredump_snapshot 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=20250703062024.3441918-4-shuicheng.lin@intel.com \
    --to=shuicheng.lin@intel.com \
    --cc=intel-xe@lists.freedesktop.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