From: Petri Latvala <petri.latvala@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH i-g-t 3/5] docs: Include subtest documentation
Date: Thu, 10 Aug 2017 13:26:49 +0300 [thread overview]
Message-ID: <1502360811-31640-4-git-send-email-petri.latvala@intel.com> (raw)
In-Reply-To: <1502360811-31640-1-git-send-email-petri.latvala@intel.com>
A simple and naive format: Double newline denotes paragraph change,
otherwise insert subtest documentation into the generated docs as-is.
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
---
docs/reference/intel-gpu-tools/Makefile.am | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/docs/reference/intel-gpu-tools/Makefile.am b/docs/reference/intel-gpu-tools/Makefile.am
index ee1e900..2407e37 100644
--- a/docs/reference/intel-gpu-tools/Makefile.am
+++ b/docs/reference/intel-gpu-tools/Makefile.am
@@ -56,6 +56,12 @@ xml/igt_test_programs_%_description.xml: $(TESTLISTS)
for subtest in $$subtest_list; do \
echo "<member>" >> $@; \
echo "$$subtest" | perl -pe 's/\b$(KEYWORDS)\b/<acronym>\1<\/acronym>/g' >> $@; \
+ subtest_doc=`./$$testprog --document-subtest $$subtest`; \
+ if [ -n "$$subtest_doc" ]; then \
+ echo "<para><![CDATA[" >> $@; \
+ echo "$$subtest_doc" | sed ':a;N;$$!ba;s,\n\n,]]></para><para><![CDATA[,g'>> $@; \
+ echo "]]></para>" >> $@; \
+ fi; \
echo "</member>" >> $@; \
done; \
echo "</simplelist>" >> $@; \
--
2.9.3
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-08-10 10:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 10:26 [PATCH i-g-t v4 0/5] Subtest documentation Petri Latvala
2017-08-10 10:26 ` [PATCH i-g-t 1/5] Add support for subtest-specific documentation Petri Latvala
2017-08-10 22:27 ` Belgaumkar, Vinay
2017-08-11 8:20 ` Daniel Vetter
2017-09-04 8:42 ` Szwichtenberg, Radoslaw
2017-09-04 8:54 ` Daniel Vetter
2017-08-10 10:26 ` [PATCH i-g-t 2/5] README: Describe the subtest documentation command line flags Petri Latvala
2017-08-10 22:59 ` Belgaumkar, Vinay
2017-08-10 10:26 ` Petri Latvala [this message]
2017-08-10 10:26 ` [PATCH i-g-t 4/5] testdisplay: Handle subtest documentation flags Petri Latvala
2017-08-10 23:08 ` Belgaumkar, Vinay
2017-08-10 10:26 ` [PATCH i-g-t 5/5] igt_command_line.sh: Test subtest documentation flag handling Petri Latvala
2017-08-10 23:09 ` Belgaumkar, Vinay
2017-08-10 10:54 ` ✓ Fi.CI.BAT: success for Subtest documentation (rev2) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2017-08-10 8:44 [PATCH i-g-t v3 0/5] Subtest documentation Petri Latvala
2017-08-10 8:44 ` [PATCH i-g-t 3/5] docs: Include subtest documentation Petri Latvala
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=1502360811-31640-4-git-send-email-petri.latvala@intel.com \
--to=petri.latvala@intel.com \
--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