All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 0/2] Enable documentation check for i915 driver
Date: Fri, 26 May 2023 08:46:22 +0200	[thread overview]
Message-ID: <20230526064624.2886063-1-mauro.chehab@linux.intel.com> (raw)

From: Mauro Carvalho Chehab <mchehab@kernel.org>

Don't let documentation to be out of sync with test changes for
i915.

The first patch contains a change on some subtsts at i915/perf_pmu
that happened after the patches adding documentation to i915.

After fixing it, we can now enable the check at build time.

Mauro Carvalho Chehab (2):
  i915/perf_pmu: sync documentation with latest changes
  testplan/meson.build: make it check for missing i915 documentation

 docs/testplan/meson.build | 4 ++--
 tests/i915/perf_pmu.c     | 8 +-------
 2 files changed, 3 insertions(+), 9 deletions(-)

-- 
2.40.1

             reply	other threads:[~2023-05-26  6:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-26  6:46 Mauro Carvalho Chehab [this message]
2023-05-26  6:46 ` [igt-dev] [PATCH i-g-t 1/2] i915/perf_pmu: sync documentation with latest changes Mauro Carvalho Chehab
2023-05-26 12:25   ` Kamil Konieczny
2023-05-26  6:46 ` [igt-dev] [PATCH i-g-t 2/2] testplan/meson.build: make it check for missing i915 documentation Mauro Carvalho Chehab
2023-05-26 12:26   ` Kamil Konieczny
2023-07-04 12:28   ` Tvrtko Ursulin
2023-07-04 12:41     ` Tvrtko Ursulin
2023-07-04 12:50       ` Mauro Carvalho Chehab
2023-07-04 13:03         ` Tvrtko Ursulin
2023-07-05  8:56           ` Mauro Carvalho Chehab
2023-07-05 15:33             ` Mauro Carvalho Chehab
2023-05-26 13:04 ` [igt-dev] ✓ Fi.CI.BAT: success for Enable documentation check for i915 driver Patchwork
2023-05-27  4:54 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20230526064624.2886063-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.