From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: John.C.Harrison@Intel.com, Intel-GFX@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH CI v2 0/4] drm/i915/guc: Update to GuC v49
Date: Thu, 22 Oct 2020 16:22:10 +0100 [thread overview]
Message-ID: <cf95a101-95c0-a28f-dca7-25c9fa9e6838@linux.intel.com> (raw)
In-Reply-To: <20201015182901.3197788-1-John.C.Harrison@Intel.com>
+ Joonas for maintainer class question.
On 15/10/2020 19:28, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> Update to the latest GuC firmware
>
> v2: Rebase to newer tree, updated a commit message (review feedback
> from Daniele) and dropped the patch to enable GuC/HuC loading by
> default as apparently this is not allowed.
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
>
>
> John Harrison (4):
> drm/i915/guc: Update to use firmware v49.0.1
> drm/i915/guc: Improved reporting when GuC fails to load
> drm/i915/guc: Clear pointers on free
> CI: turn on GuC/HuC auto mode by default
>
> drivers/gpu/drm/i915/gt/intel_engine_cs.c | 3 +-
> drivers/gpu/drm/i915/gt/uc/intel_guc.c | 18 ---
> drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 132 +++++++++++++++----
> drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 1 +
> drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c | 31 +++--
> drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h | 80 +++++------
> drivers/gpu/drm/i915/gt/uc/intel_guc_reg.h | 5 +
> drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 29 ++--
> drivers/gpu/drm/i915/gt/uc/intel_uc_fw.h | 2 +
> drivers/gpu/drm/i915/gt/uc/intel_uc_fw_abi.h | 6 +-
> drivers/gpu/drm/i915/i915_params.h | 2 +-
> 11 files changed, 202 insertions(+), 107 deletions(-)
I tried to merge this for John today but the series applies to
drm-intel-next-queued and not drm-intel-gt-next, which I thought is
where GT/GuC should go to. Long story short, where to merge GuC patches
and how is the question?
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-10-22 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 18:28 [Intel-gfx] [PATCH CI v2 0/4] drm/i915/guc: Update to GuC v49 John.C.Harrison
2020-10-15 18:28 ` [Intel-gfx] [PATCH CI v2 1/4] drm/i915/guc: Update to use firmware v49.0.1 John.C.Harrison
2020-10-15 18:28 ` [Intel-gfx] [PATCH CI v2 2/4] drm/i915/guc: Improved reporting when GuC fails to load John.C.Harrison
2020-10-15 18:29 ` [Intel-gfx] [PATCH CI v2 3/4] drm/i915/guc: Clear pointers on free John.C.Harrison
2020-10-15 18:29 ` [Intel-gfx] [PATCH CI v2 4/4] CI: turn on GuC/HuC auto mode by default John.C.Harrison
2020-10-15 19:41 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/guc: Update to GuC v49 Patchwork
2020-10-15 20:07 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-10-16 0:08 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-10-22 15:22 ` Tvrtko Ursulin [this message]
2020-10-23 6:24 ` [Intel-gfx] [PATCH CI v2 0/4] " Joonas Lahtinen
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=cf95a101-95c0-a28f-dca7-25c9fa9e6838@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-GFX@Lists.FreeDesktop.Org \
--cc=John.C.Harrison@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