From: Daniel Vetter <daniel@ffwll.ch>
To: Thomas Wood <thomas.wood@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [i-g-t 7/7] docs: add missing sections to intel-gpu-tools-docs.xml
Date: Tue, 10 Jun 2014 16:47:07 +0200 [thread overview]
Message-ID: <20140610144707.GX5821@phenom.ffwll.local> (raw)
In-Reply-To: <1402410657-4768-7-git-send-email-thomas.wood@intel.com>
On Tue, Jun 10, 2014 at 03:30:57PM +0100, Thomas Wood wrote:
> Signed-off-by: Thomas Wood <thomas.wood@intel.com>
I've intentionally left these out since they're not really part of the
core test library ... E.g. all public rendercopy functions are documented
as part of the "intel batchbuffer" library.
-Daniel
> ---
> docs/reference/intel-gpu-tools/intel-gpu-tools-docs.xml | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/docs/reference/intel-gpu-tools/intel-gpu-tools-docs.xml b/docs/reference/intel-gpu-tools/intel-gpu-tools-docs.xml
> index dcfff33..96cf77f 100644
> --- a/docs/reference/intel-gpu-tools/intel-gpu-tools-docs.xml
> +++ b/docs/reference/intel-gpu-tools/intel-gpu-tools-docs.xml
> @@ -15,6 +15,7 @@
>
> <chapter>
> <title>Intel GPU Tools</title>
> + <xi:include href="xml/debug.xml"/>
> <xi:include href="xml/drmtest.xml"/>
> <xi:include href="xml/igt_core.xml"/>
> <xi:include href="xml/igt_debugfs.xml"/>
> @@ -22,9 +23,12 @@
> <xi:include href="xml/igt_fb.xml"/>
> <xi:include href="xml/igt_aux.xml"/>
> <xi:include href="xml/ioctl_wrappers.xml"/>
> + <xi:include href="xml/instdone.xml"/>
> <xi:include href="xml/intel_batchbuffer.xml"/>
> <xi:include href="xml/intel_chipset.xml"/>
> <xi:include href="xml/intel_io.xml"/>
> + <xi:include href="xml/media_fill.xml"/>
> + <xi:include href="xml/rendercopy.xml"/>
>
> </chapter>
> <index id="api-index-full">
> --
> 1.9.3
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-06-10 14:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 14:30 [i-g-t 1/7] README: update piglit instructions Thomas Wood
2014-06-10 14:30 ` [i-g-t 2/7] lib: remove /** from comments that are not API documentation Thomas Wood
2014-06-10 14:30 ` [i-g-t 3/7] README: update the section on modifying and rebuilding documentation Thomas Wood
2014-06-10 14:38 ` Daniel Vetter
2014-06-11 10:33 ` Thomas Wood
2014-06-10 14:30 ` [i-g-t 4/7] docs: add the sections file Thomas Wood
2014-06-10 14:40 ` Daniel Vetter
2014-06-11 10:35 ` Thomas Wood
2014-06-11 11:56 ` Daniel Vetter
2014-06-11 14:49 ` [PATCH i-g-t] docs: always rebuild " Thomas Wood
2014-06-10 14:30 ` [i-g-t 5/7] gitignore: add missing files and keep lists sorted Thomas Wood
2014-06-10 14:30 ` [i-g-t 6/7] lib: various documentation fixes Thomas Wood
2014-06-10 14:44 ` Daniel Vetter
2014-06-10 14:30 ` [i-g-t 7/7] docs: add missing sections to intel-gpu-tools-docs.xml Thomas Wood
2014-06-10 14:47 ` Daniel Vetter [this message]
2014-06-11 10:36 ` Thomas Wood
2014-06-11 10:53 ` [PATCH i-g-t] docs: add private headers to IGNORE_HFILES Thomas Wood
2014-06-11 11:57 ` Daniel Vetter
2014-06-10 14:37 ` [i-g-t 1/7] README: update piglit instructions Daniel Vetter
2014-06-10 15:06 ` Thomas Wood
2014-06-10 15:28 ` 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=20140610144707.GX5821@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thomas.wood@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