From: Katarzyna Piecielska <katarzyna.piecielska@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Katarzyna Piecielska <katarzyna.piecielska@intel.com>,
Kamil Konieczny <kamil.konieczny@intel.com>,
Jari Tahvanainen <jari.tahvanainen@intel.com>,
Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
Subject: [PATCH i-g-t v2 0/3] Put "Run type" highest in documentation hierarchy
Date: Tue, 23 Apr 2024 09:53:41 +0000 [thread overview]
Message-ID: <20240423095344.3518545-1-katarzyna.piecielska@intel.com> (raw)
Let's put "Run type" at highest place in documentation hierarchy. It
will be reflected in html generated documentation.
v2: Make that change in Xe, i915 and KMS (Mauro)
Signed-off-by: Katarzyna Piecielska <katarzyna.piecielska@intel.com>
Cc: Kamil Konieczny <kamil.konieczny@intel.com>
Cc: Jari Tahvanainen <jari.tahvanainen@intel.com>
Cc: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
Katarzyna Piecielska (3):
tests/intel: Put "Run type" highest in Xe documentation hierarchy
tests/intel: Put "Run type" highest in KMS documentation hierarchy
tests/intel: Put "Run type" highest in i915 documentation hierarchy
tests/intel/i915_test_config.json | 150 +++++++++++++++---------------
tests/intel/kms_test_config.json | 94 +++++++++----------
tests/intel/xe_test_config.json | 66 ++++++-------
3 files changed, 155 insertions(+), 155 deletions(-)
--
2.34.1
next reply other threads:[~2024-04-23 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 9:53 Katarzyna Piecielska [this message]
2024-04-23 9:53 ` [PATCH i-g-t v2 1/3] tests/intel: Put "Run type" highest in Xe documentation hierarchy Katarzyna Piecielska
2024-04-23 9:53 ` [PATCH i-g-t v2 2/3] tests/intel: Put "Run type" highest in KMS " Katarzyna Piecielska
2024-04-24 7:42 ` Mauro Carvalho Chehab
2024-04-23 9:53 ` [PATCH i-g-t v2 3/3] tests/intel: Put "Run type" highest in i915 " Katarzyna Piecielska
2024-04-24 7:45 ` Mauro Carvalho Chehab
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=20240423095344.3518545-1-katarzyna.piecielska@intel.com \
--to=katarzyna.piecielska@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jari.tahvanainen@intel.com \
--cc=kamil.konieczny@intel.com \
--cc=mauro.chehab@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