From: Matthew Brost <matthew.brost@intel.com>
To: <intel-gfx@lists.freedesktop.org>, <dri-devel@lists.freedesktop.org>
Subject: [Intel-gfx] [PATCH 0/2] A couple more prerequisite patches to GuC submission
Date: Wed, 26 May 2021 14:30:27 -0700 [thread overview]
Message-ID: <20210526213029.7178-1-matthew.brost@intel.com> (raw)
As discussed in [1] we are breaking that large series into a several
smaller ones. This series includes 2 patches with no other dependencies
and are fully reviewed discussed as part of step #4.
Assuming CI looks good these patches can be merged immediately.
[1] https://patchwork.freedesktop.org/series/89844/
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Daniele Ceraolo Spurio (1):
drm/i915/guc: Use guc_class instead of engine_class in fw interface
Michal Wajdeczko (1):
drm/i915/guc: Early initialization of GuC send registers
drivers/gpu/drm/i915/gt/intel_engine_cs.c | 6 +++--
drivers/gpu/drm/i915/gt/uc/intel_guc.c | 18 +++++++-------
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 20 +++++++++-------
drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h | 26 +++++++++++++++++++++
4 files changed, 51 insertions(+), 19 deletions(-)
--
2.28.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2021-05-26 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 21:30 Matthew Brost [this message]
2021-05-26 21:30 ` [Intel-gfx] [PATCH 1/2] drm/i915/guc: Early initialization of GuC send registers Matthew Brost
2021-05-26 21:30 ` [Intel-gfx] [PATCH 2/2] drm/i915/guc: Use guc_class instead of engine_class in fw interface Matthew Brost
2021-05-27 1:47 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for A couple more prerequisite patches to GuC submission Patchwork
2021-05-27 2:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-05-27 17:21 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20210526213029.7178-1-matthew.brost@intel.com \
--to=matthew.brost@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