From: John.C.Harrison@Intel.com
To: Intel-GFX@Lists.FreeDesktop.Org
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: [Intel-gfx] [PATCH 0/3] Fixes for various UC related issues
Date: Wed, 21 Dec 2022 11:30:28 -0800 [thread overview]
Message-ID: <20221221193031.687266-1-John.C.Harrison@Intel.com> (raw)
From: John Harrison <John.C.Harrison@Intel.com>
Fix a bunch of assorted issues with firmware loading and GuC
intialisation.
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
John Harrison (3):
drm/i915/guc: Fix missing return code checks in submission init
drm/i915/guc: Fix a static analysis warning
drm/i915/uc: Fix two issues with over-size firmware files
.../gpu/drm/i915/gt/uc/intel_guc_submission.c | 75 ++++++++++++++-----
.../gpu/drm/i915/gt/uc/intel_guc_submission.h | 2 +-
drivers/gpu/drm/i915/gt/uc/intel_uc.c | 7 +-
drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 42 +++++++----
4 files changed, 91 insertions(+), 35 deletions(-)
--
2.39.0
next reply other threads:[~2022-12-21 19:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 19:30 John.C.Harrison [this message]
2022-12-21 19:30 ` [Intel-gfx] [PATCH 1/3] drm/i915/guc: Fix missing return code checks in submission init John.C.Harrison
2022-12-22 12:56 ` Ceraolo Spurio, Daniele
2022-12-21 19:30 ` [Intel-gfx] [PATCH 2/3] drm/i915/guc: Fix a static analysis warning John.C.Harrison
2022-12-22 12:57 ` Ceraolo Spurio, Daniele
2022-12-21 19:30 ` [Intel-gfx] [PATCH 3/3] drm/i915/uc: Fix two issues with over-size firmware files John.C.Harrison
2022-12-22 11:09 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fixes for various UC related issues (rev2) Patchwork
2022-12-22 11:09 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-12-22 11:39 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-12-22 16:43 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-12-20 2:41 [Intel-gfx] [PATCH 0/3] Fixes for various UC related issues John.C.Harrison
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=20221221193031.687266-1-John.C.Harrison@Intel.com \
--to=john.c.harrison@intel.com \
--cc=DRI-Devel@Lists.FreeDesktop.Org \
--cc=Intel-GFX@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