From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: Fix GuC documentation links
Date: Wed, 24 Jul 2019 10:43:49 -0700 [thread overview]
Message-ID: <43499e9a-ba2f-2da3-e85b-8c494b11ff9f@intel.com> (raw)
In-Reply-To: <20190724173446.35188-1-michal.wajdeczko@intel.com>
On 7/24/19 10:34 AM, Michal Wajdeczko wrote:
> We moved GuC related files to new location but we missed to update
> .rst file with links.
>
> References: commit 0f261b241d9c ("drm/i915/uc: move GuC and HuC files under gt/uc/")
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
That's all of them (which surprised me since I expected an entry for HuC
as well).
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> ---
> Documentation/gpu/i915.rst | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/gpu/i915.rst b/Documentation/gpu/i915.rst
> index c38ef0dda605..c2173d120492 100644
> --- a/Documentation/gpu/i915.rst
> +++ b/Documentation/gpu/i915.rst
> @@ -433,28 +433,28 @@ GuC
> GuC-specific firmware loader
> ----------------------------
>
> -.. kernel-doc:: drivers/gpu/drm/i915/intel_guc_fw.c
> +.. kernel-doc:: drivers/gpu/drm/i915/gt/uc/intel_guc_fw.c
> :internal:
>
> GuC-based command submission
> ----------------------------
>
> -.. kernel-doc:: drivers/gpu/drm/i915/intel_guc_submission.c
> +.. kernel-doc:: drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> :doc: GuC-based command submission
>
> -.. kernel-doc:: drivers/gpu/drm/i915/intel_guc_submission.c
> +.. kernel-doc:: drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> :internal:
>
> GuC Firmware Layout
> -------------------
>
> -.. kernel-doc:: drivers/gpu/drm/i915/intel_guc_fwif.h
> +.. kernel-doc:: drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h
> :doc: GuC Firmware Layout
>
> GuC Address Space
> -----------------
>
> -.. kernel-doc:: drivers/gpu/drm/i915/intel_guc.c
> +.. kernel-doc:: drivers/gpu/drm/i915/gt/uc/intel_guc.c
> :doc: GuC Address Space
>
> Tracing
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-07-24 17:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 17:34 [PATCH 1/3] drm/i915: Fix GuC documentation links Michal Wajdeczko
2019-07-24 17:34 ` [PATCH 2/3] drm/i915/uc: Move uc firmware layout definitions to dedicated file Michal Wajdeczko
2019-07-24 17:50 ` Daniele Ceraolo Spurio
2019-07-24 20:01 ` Michal Wajdeczko
2019-07-24 20:05 ` Daniele Ceraolo Spurio
2019-07-24 17:34 ` [PATCH 3/3] drm/i915/uc: Update drawing for firmware layout Michal Wajdeczko
2019-07-24 17:44 ` Daniele Ceraolo Spurio
2019-07-24 20:09 ` Michal Wajdeczko
2019-07-24 20:11 ` Daniele Ceraolo Spurio
2019-07-24 17:43 ` Daniele Ceraolo Spurio [this message]
2019-07-24 17:51 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915: Fix GuC documentation links Patchwork
2019-07-24 19:49 ` ✓ Fi.CI.BAT: success " Patchwork
2019-07-24 21:56 ` ✓ 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=43499e9a-ba2f-2da3-e85b-8c494b11ff9f@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.wajdeczko@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