From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 0/5] Do dome cleanups at IGT doc tools
Date: Tue, 28 Nov 2023 11:48:55 +0100 [thread overview]
Message-ID: <20231128105054.24317-1-mauro.chehab@linux.intel.com> (raw)
From: Mauro Carvalho Chehab <mchehab@kernel.org>
This series is aimed to do some cleanup at documentation testlist
scripts, solving some issues pointed by pylint and reorganizing
the code.
The first two patches were already reviewed. This series have them
at the beginning, untouched.
Mauro Carvalho Chehab (5):
scripts/test_list.py: better expand subtests
scripts/test_list.py: don't add a blank description
scripts/test_list.py: Fix trivial pylint issues
scripts/test_list.py: fix indent at get_subtests()
igt_doc.py: move the main code to a main() function
scripts/igt_doc.py | 122 +++++++++++++++++++++++--------------------
scripts/test_list.py | 95 +++++++++++++++++----------------
2 files changed, 114 insertions(+), 103 deletions(-)
--
2.42.0
next reply other threads:[~2023-11-28 10:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 10:48 Mauro Carvalho Chehab [this message]
2023-11-28 10:48 ` [igt-dev] [PATCH i-g-t 1/5] scripts/test_list.py: better expand subtests Mauro Carvalho Chehab
2023-11-28 10:48 ` [igt-dev] [PATCH i-g-t 2/5] scripts/test_list.py: don't add a blank description Mauro Carvalho Chehab
2023-11-28 15:51 ` Kamil Konieczny
2023-11-28 10:48 ` [igt-dev] [PATCH i-g-t 3/5] scripts/test_list.py: Fix trivial pylint issues Mauro Carvalho Chehab
2023-11-28 15:44 ` Kamil Konieczny
2023-11-28 10:48 ` [igt-dev] [PATCH i-g-t 4/5] scripts/test_list.py: fix indent at get_subtests() Mauro Carvalho Chehab
2023-11-28 15:57 ` Kamil Konieczny
2023-11-28 10:49 ` [igt-dev] [PATCH i-g-t 5/5] igt_doc.py: move the main code to a main() function Mauro Carvalho Chehab
2023-11-28 15:59 ` Kamil Konieczny
2023-11-28 11:59 ` [igt-dev] ✓ CI.xeBAT: success for Do dome cleanups at IGT doc tools 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=20231128105054.24317-1-mauro.chehab@linux.intel.com \
--to=mauro.chehab@linux.intel.com \
--cc=igt-dev@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