From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: Katarzyna Dec <katarzyna.dec@intel.com>
Cc: igt-dev@lists.freedesktop.org, Gandi Ramadevi <ramadevi.gandi@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 0/2] IGT XE documentation cleanup
Date: Thu, 31 Aug 2023 15:00:26 +0200 [thread overview]
Message-ID: <20230831150026.01ce20f6@maurocar-mobl2> (raw)
In-Reply-To: <20230831143040.11f82c2b@maurocar-mobl2>
On Thu, 31 Aug 2023 14:30:40 +0200
Mauro Carvalho Chehab <mauro.chehab@linux.intel.com> wrote:
> On Thu, 31 Aug 2023 11:39:34 +0000
> Katarzyna Dec <katarzyna.dec@intel.com> wrote:
>
> > Let's add missing documentation fileds that are causing warnings.
> > Some tests documentation needed changes to have more accurate naming.
> > Let's mark Negative and Stress tests.
> > Adding missing 'Run type' and 'Test category' for remaining test.
>
> Kasia,
>
> Besides the changes, could you please also change the
> sub-category field and/or Functionalities for xe_mmap.c?
>
> Right now, both are using "mmap" bucket. This is valid for
> the documentation itself, but it causes confusion when analyzing
> the results later on, as there will be two buckets with the same
> name but different meanings.
>
> Perhaps we could use Sub-category == "VMA".
>
> What do you think?
>
> Another issue I noticed in this series is that we have "Blitter"
> with the first letter in uppercase. Perhaps there are more cases like
> that. Please let's use lowercase on such buckets, as this is less
> prone to errors (IMO).
Another thing: I would add this patch at the end of the series:
https://patchwork.freedesktop.org/series/123111/
This will enforce CI to check for incomplete documentation at
build time, aborting the build (and producing CI errors) if the
documentation is not there.
Regards,
Mauro
next prev parent reply other threads:[~2023-08-31 13:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 11:39 [igt-dev] [PATCH i-g-t 0/2] IGT XE documentation cleanup Katarzyna Dec
2023-08-31 11:39 ` [igt-dev] [PATCH i-g-t 1/2] tests/xe: Add missing documentation fields for tests Katarzyna Dec
2023-08-31 12:32 ` Mauro Carvalho Chehab
2023-08-31 11:39 ` [igt-dev] [PATCH i-g-t 2/2] test/xe: Clean up of test documentation Katarzyna Dec
2023-08-31 12:35 ` Mauro Carvalho Chehab
2023-08-31 12:18 ` [igt-dev] ✗ GitLab.Pipeline: warning for IGT XE documentation cleanup Patchwork
2023-08-31 12:30 ` [igt-dev] [PATCH i-g-t 0/2] " Mauro Carvalho Chehab
2023-08-31 13:00 ` Mauro Carvalho Chehab [this message]
2023-08-31 12:53 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-08-31 13:53 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-08-31 15:57 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=20230831150026.01ce20f6@maurocar-mobl2 \
--to=mauro.chehab@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=katarzyna.dec@intel.com \
--cc=ramadevi.gandi@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