From: Graham Whaley <graham.whaley@linux.intel.com>
To: daniel.vetter@intel.com, jani.nikula@linux.intel.com,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Graham Whaley <graham.whaley@linux.intel.com>
Subject: [PATCH] doc: drm: Fix mis-spelling of i915_guc_submission includes
Date: Mon, 24 Aug 2015 14:41:21 +0100 [thread overview]
Message-ID: <1440423681-11825-1-git-send-email-graham.whaley@linux.intel.com> (raw)
In commit
d1675198e: drm/i915: Integrate GuC-based command submission
the drm.tmpl include lines reference the intel_guc_submission.c but the
patch adds the file i915_guc_submission.c. drm.tmpl fails to build with:
docproc: .//drivers/gpu/drm/i915/intel_guc_submission.c:
No such file or directory
Change the file reference to the actual file.
Signed-off-by: Graham Whaley <graham.whaley@linux.intel.com>
---
This looks/feels like the right fix to me, but I am not intimate enough
with the APIs to verify for sure - some confirmation would be good.
Documentation/DocBook/drm.tmpl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl
index a01fca9..66bc646 100644
--- a/Documentation/DocBook/drm.tmpl
+++ b/Documentation/DocBook/drm.tmpl
@@ -4160,8 +4160,8 @@ int num_ioctls;</synopsis>
</sect2>
<sect2>
<title>GuC Client</title>
-!Pdrivers/gpu/drm/i915/intel_guc_submission.c GuC-based command submissison
-!Idrivers/gpu/drm/i915/intel_guc_submission.c
+!Pdrivers/gpu/drm/i915/i915_guc_submission.c GuC-based command submissison
+!Idrivers/gpu/drm/i915/i915_guc_submission.c
</sect2>
</sect1>
--
2.4.3
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2015-08-24 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 13:41 Graham Whaley [this message]
2015-08-25 9:24 ` [PATCH] doc: drm: Fix mis-spelling of i915_guc_submission includes Daniel Vetter
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=1440423681-11825-1-git-send-email-graham.whaley@linux.intel.com \
--to=graham.whaley@linux.intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.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