All of lore.kernel.org
 help / color / mirror / Atom feed
* [igt-dev] [PATCH 0/2] Introduce MAINTAINERS file to IGT
@ 2022-02-17 15:26 Rodrigo Siqueira
  2022-02-17 15:26 ` [igt-dev] [PATCH 1/2] MAINTAINERS: Introduce MAINTAINERS file Rodrigo Siqueira
                   ` (4 more replies)
  0 siblings, 5 replies; 10+ messages in thread
From: Rodrigo Siqueira @ 2022-02-17 15:26 UTC (permalink / raw)
  To: Arkadiusz Hiler, Petri Latvala
  Cc: igt-dev, Bhawanpreet Lakha, Qingqing Zhuo, Solomon Chiu,
	Sean Paul, Mark Yacoub

IGT is becoming more generic, and multiple vendors are adopting it. For
example, AMD fully upstream all of its internal changes last year, and
now we are relying on IGT from the upstream. Additionally, thanks to the
ChromeOS project, we have other vendors working on the KMS tests as
well. At this point, I believe that we need some mechanism to better
contact developers that care about some specific tests or even provide
an easy way for other people to find the right stakeholder for dealing
with some particular issue.

Imho Linux Kernel already has a good solution codified in the
MAINTAINERS and get_maintainers files. One of the best things about this
approach was adding reviewers and maintainers (and other options) to the
specific part of the code and using the get_maintainers tool to extract
the right people to be part of the series. With this idea in mind, I
created an RFC that introduces the MAINTAINERS file in IGT, and
collected feedback. This series is the first version that introduces the
MAINTAINERS and a wrapper to the get_maintainers file.

For this series, I recommend:

1. Patch 1: It has the maintainers file. If you want to add yourself to
some specific test, please, let me know in this patch.
2. Patch 2: get_maintainers wrapper, see the CONTRIBUTING page on how to
use it.

Cc: Arkadiusz Hiler <arek@hiler.eu>
Cc: Petri Latvala <petri.latvala@intel.com>
Cc: Mark Yacoub <markyacoub@google.com>
Cc: Jessica Zhang <quic_jesszhan@quicinc.com>
Cc: Abhinav Kumar <quic_abhinavk@quicinc.com>
Cc: Melissa Wen <mwen@igalia.com>
Cc: Sean Paul <seanpaul@chromium.org>
Cc: Harry Wentland <harry.wentland@amd.com>
Cc: Sun Peng Li(Leo) <sunpeng.li@amd.com>
Cc: Chao-kai Wang (Stylon) <stylon.wang@amd.com>
Cc: Wayne Lin <wayne.lin@amd.com>
Cc: Nicholas Choi <nicholas.choi@amd.com>
Cc: Martin Peres <martin.peres@mupuf.org>
Cc: Aurabindo Pillai <aurabindo.pillai@amd.com>
Cc: Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
Cc: Qingqing Zhuo (Lilian) <qingqing.zhuo@amd.com>
Cc: Solomon Chiu <solomon.chiu@amd.com>
Cc: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Cc: Dingchen Zhang (David) <Dingchen.Zhang@amd.com>

Rodrigo Siqueira (2):
  MAINTAINERS: Introduce MAINTAINERS file
  scripts: get_maintainer: Introduce get_maintainer wrapper

 .gitignore                |   1 +
 CONTRIBUTING.md           |  17 +++-
 MAINTAINERS               | 198 +++++++++++++++++++++++++++++++++++++-
 scripts/get_maintainer.sh | 104 ++++++++++++++++++++
 4 files changed, 317 insertions(+), 3 deletions(-)
 create mode 100755 scripts/get_maintainer.sh

-- 
2.25.1

^ permalink raw reply	[flat|nested] 10+ messages in thread

* [igt-dev] [PATCH 1/2] MAINTAINERS: Introduce MAINTAINERS file
  2022-02-17 15:26 [igt-dev] [PATCH 0/2] Introduce MAINTAINERS file to IGT Rodrigo Siqueira
@ 2022-02-17 15:26 ` Rodrigo Siqueira
  2022-03-01 16:10   ` Harry Wentland
  2022-03-01 18:45   ` Melissa Wen
  2022-02-17 15:26 ` [igt-dev] [PATCH 2/2] scripts: get_maintainer: Introduce get_maintainer wrapper Rodrigo Siqueira
                   ` (3 subsequent siblings)
  4 siblings, 2 replies; 10+ messages in thread
From: Rodrigo Siqueira @ 2022-02-17 15:26 UTC (permalink / raw)
  To: Arkadiusz Hiler, Petri Latvala
  Cc: igt-dev, Bhawanpreet Lakha, Qingqing Zhuo, Solomon Chiu,
	Sean Paul, Mark Yacoub

IGT is growing in terms of new vendors actively using it. Right now, we
only have Intel CI to validate new patches, which can create a situation
where bugs get accidentally introduced to other vendors. To alleviate
this problem and also making easy for other developers to be aware of
some specific changes, I'm proposing the introduction of the MAINTAINERS
file as the one used in the Linux kernel. With this approach, we can
have multiple enginers from different companies as reviewers for
specific tests, and contributors should use get_maintainers script to
find the right people to address their changes.

Cc: Arkadiusz Hiler <arek@hiler.eu>
Cc: Petri Latvala <petri.latvala@intel.com>
Cc: Mark Yacoub <markyacoub@google.com>
Cc: Jessica Zhang <quic_jesszhan@quicinc.com>
Cc: Abhinav Kumar <quic_abhinavk@quicinc.com>
Cc: Melissa Wen <mwen@igalia.com>
Cc: Sean Paul <seanpaul@chromium.org>
Cc: Harry Wentland <harry.wentland@amd.com>
Cc: Sun Peng Li(Leo) <sunpeng.li@amd.com>
Cc: Chao-kai Wang (Stylon) <stylon.wang@amd.com>
Cc: Wayne Lin <wayne.lin@amd.com>
Cc: Nicholas Choi <nicholas.choi@amd.com>
Cc: Martin Peres <martin.peres@mupuf.org>
Cc: Aurabindo Pillai <aurabindo.pillai@amd.com>
Cc: Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
Cc: Qingqing Zhuo (Lilian) <qingqing.zhuo@amd.com>
Cc: Solomon Chiu <solomon.chiu@amd.com>
Cc: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Cc: Dingchen Zhang (David) <Dingchen.Zhang@amd.com>

Signed-off-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
---
 MAINTAINERS | 198 +++++++++++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 196 insertions(+), 2 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 383c327c..fac605de 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1,2 +1,196 @@
-Petri Latvala <petri.latvala@intel.com>
-Arkadiusz Hiler <arek@hiler.eu>
+List of maintainers/reviewers to submit IGT changes
+===================================================
+
+Please try to follow the guidelines below.  This will make things
+easier on the maintainers.  Not all of these guidelines matter for every
+trivial patch so apply some common sense.
+
+Tips for patch submitters
+-------------------------
+
+1.	Always *test* your changes.
+
+2.	Make sure your changes compile correctly.
+
+3.	When you are happy with a change make it generally available for
+	testing and await feedback.
+
+4.	Make a patch available to the relevant maintainer in the list. Be prepared
+	to get your changes sent back with seemingly silly requests about
+	formatting and variable names. These aren't as silly as they seem. One job
+	the maintainers do is to keep things looking the same.
+
+	PLEASE CC: the maintainers and mailing lists that are generated
+	by ``scripts/get_maintainer.sh.`` The results returned by the
+	script will be best if you have git installed.
+
+	PLEASE try to include any credit lines you want added with the
+	patch. It avoids people being missed off by mistake and makes
+	it easier to know who wants adding and who doesn't.
+
+	PLEASE document known bugs.
+
+5.	Make sure you have the right to send any changes you make. If you
+	do changes at work you may find your employer owns the patch
+	not you.
+
+Descriptions of section entries and preferred order
+---------------------------------------------------
+
+	M: *Mail* patches to: FullName <address@domain>
+	R: Designated *Reviewer*: FullName <address@domain>
+	   These reviewers should be CCed on patches.
+	L: *Mailing list* that is relevant to this area
+	S: *Status*, one of the following:
+	   Supported:	Someone is actually paid to look after this.
+	   Maintained:	Someone actually looks after it.
+	W: *Web-page* with status/info
+	Q: *Patchwork* web based patch tracking system site
+	B: URI for where to file *bugs*. A web-page with detailed bug
+	   filing info, a direct bug tracker link, or a mailto: URI.
+	C: URI for *chat* protocol, server and channel where developers
+	   usually hang out, for example irc://server/channel.
+	T: *SCM* tree type and location.
+	   Type is one of: git, hg, quilt, stgit, topgit
+	F: *Files* and directories wildcard patterns.
+	   A trailing slash includes all files and subdirectory files.
+	   F:	tests/amdgpu/	all files in and below tests/amdgpu
+	   F:	tests/*	all files in tests/, but not below
+	   One pattern per line.  Multiple F: lines acceptable.
+	X: *Excluded* files and directories that are NOT maintained, same
+	   rules as F:. Files exclusions are tested before file matches.
+
+Maintainers List
+----------------
+
+KMS Generic API tests
+R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
+R:	Qingqing Zhuo (Lilian) <Qingqing.Zhuo@amd.com@amd.com>
+R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
+F:	tests/kms_atomic.c
+F:	tests/kms_atomic_interruptible.c
+F:	tests/kms_atomic_transition.c
+F:	tests/kms_properties.c
+F:	tests/kms_setmode.c
+F:	tests/kms_concurrent.c
+F:	tests/kms_prop_blob.c
+F:	tests/kms_multipipe_modeset.c
+
+KMS CRC API
+R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
+R:	Sunpeng Li (Leo) <Sunpeng.Li@amd.com>
+R:	Dingchen Zhang (David) <Dingchen.Zhang@amd.com>
+R:	Melissa Wen <mwen@igalia.com>
+F:	tests/kms_cursor_crc.c
+F:	tests/kms_pipe_crc_basic.c
+F:	tests/kms_rotation_crc.c
+
+KMS HDR
+R:	Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
+
+KMS Color
+R:	Stylon Wang <stylon.wang@amd.com>
+R:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
+R:	Sunpeng Li (Leo) <Sunpeng.Li@amd.com>
+F:	tests/kms_color.c
+
+KMS Content protection
+R:	Dingchen Zhang (David) <Dingchen.Zhang@amd.com>
+R:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
+F:	tests/kms_content_protection.c
+
+KMS Cursor tests
+R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
+R:	Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
+F:	tests/kms_cursor_legacy.c
+F:	tests/kms_cursor_edge_walk.c
+F:	tests/kms_plane_cursor.c
+F:	tests/kms_plane_alpha_blend.c
+
+VRR tests
+R:	Stylon Wang <stylon.wang@amd.com>
+R:	Wayne Lin <Wayne.Lin@amd.com>
+R:	Solomon Chiu <Solomon.Chiu@amd.com>
+R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
+R:	Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
+S:	Maintained
+F:	tests/kms_vrr.c
+
+KMS Vblank tests
+R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
+R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
+S:	Maintained
+F:	tests/kms_vblank.c
+
+KMS Flip tests
+R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
+R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
+S:	Maintained
+F:	tests/kms_flip.c
+F:	tests/kms_flip_event_leak.c
+
+KMS plane tests
+R:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
+R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
+R:	Stylon Wang <stylon.wang@amd.com>
+S:	Maintained
+F:	tests/kms_plane.c
+F:	tests/kms_plane_scaling.c
+
+KMS Bandwidth
+R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
+F:	tests/kms_bw.c
+
+AMDGPU
+M:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
+M:	Stylon Wang <stylon.wang@amd.com>
+M:	Wayne Lin <Wayne.Lin@amd.com>
+S:	Maintained
+F:	tests/amdgpu/*
+
+AMDGPU AMD Plane
+M:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
+F:	tests/amdgpu/amd_plane.c
+
+AMDGPU AMD Link
+M:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
+F:	tests/amdgpu/amd_link_settings.c
+F:	tests/amdgpu/amd_dp_dsc.c
+F:	tests/amdgpu/amd_hotplug.c
+
+AMDGPU AMD Color
+M:	Stylon Wang <stylon.wang@amd.com>
+R:	Sunpeng Li (Leo) <Sunpeng.Li@amd.com>
+R:	Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
+F:	tests/amdgpu/amd_color.c
+F:	tests/amdgpu/amd_max_bpc.c
+
+AMDGPU AMD content protection
+M:	Stylon Wang <stylon.wang@amd.com>
+R:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
+F:	tests/amdgpu/amd_assr.c
+
+AMDGPU VRR/Freesync
+M:	Stylon Wang <stylon.wang@amd.com>
+M:	Solomon Chiu <Solomon.Chiu@amd.com>
+R:	Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
+R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
+F:	tests/amdgpu/amd_vrr_range.c
+
+All KMS tests
+R:	Mark Yacoub <markyacoub@chromium.org>
+F:	tests/kms_*
+
+V3D tests
+R:	Melissa Wen <mwen@igalia.com>
+F:	tests/v3d_*
+
+THE REST
+M:	Arkadiusz Hiler <arek@hiler.eu>
+M:	Petri Latvala <petri.latvala@intel.com>
+L:	igt-dev@lists.freedesktop.org
+B:	https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues
+Q:	https://patchwork.freedesktop.org/project/igt/series/?ordering=-last_updated
+T:	git@gitlab.freedesktop.org:drm/igt-gpu-tools.git
+F:	*
+F:	*/
-- 
2.25.1

^ permalink raw reply related	[flat|nested] 10+ messages in thread

* [igt-dev] [PATCH 2/2] scripts: get_maintainer: Introduce get_maintainer wrapper
  2022-02-17 15:26 [igt-dev] [PATCH 0/2] Introduce MAINTAINERS file to IGT Rodrigo Siqueira
  2022-02-17 15:26 ` [igt-dev] [PATCH 1/2] MAINTAINERS: Introduce MAINTAINERS file Rodrigo Siqueira
@ 2022-02-17 15:26 ` Rodrigo Siqueira
  2022-02-17 16:00 ` [igt-dev] ✓ Fi.CI.BAT: success for Introduce MAINTAINERS file to IGT (rev2) Patchwork
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 10+ messages in thread
From: Rodrigo Siqueira @ 2022-02-17 15:26 UTC (permalink / raw)
  To: Arkadiusz Hiler, Petri Latvala
  Cc: igt-dev, Bhawanpreet Lakha, Qingqing Zhuo, Solomon Chiu,
	Sean Paul, Mark Yacoub

Linux kernel has a script that parses the MAINTAINERS files, and it is
well maintained in the upstream. Based on that, I want to avoid
reinventing the wheel and reduce our maintenance work by not duplicating
the kernel effort. This commit introduces a wrapper script to the
get_maintainers.pl file; in summary, it only provides these features:

* List of developers
* Mailing list
* List of developers and list together
* It accepts a file path
* It accepts a patch
(I tried to keep this wrapper as minimal as possible).
A simple usage example is:

  scripts/get_maintainer.sh devs tests/kms_plane.c

or

  scripts/get_maintainer.sh list tests/kms_plane.c

Notice that this script can be integrated to git-send-email (see updates
in the CONTRIBUTING file).

Cc: Arkadiusz Hiler <arek@hiler.eu>
Cc: Petri Latvala <petri.latvala@intel.com>
Cc: Mark Yacoub <markyacoub@google.com>
Cc: Jessica Zhang <quic_jesszhan@quicinc.com>
Cc: Abhinav Kumar <quic_abhinavk@quicinc.com>
Cc: Melissa Wen <mwen@igalia.com>
Cc: Sean Paul <seanpaul@chromium.org>
Cc: Harry Wentland <harry.wentland@amd.com>
Cc: Sun Peng Li(Leo) <sunpeng.li@amd.com>
Cc: Chao-kai Wang (Stylon) <stylon.wang@amd.com>
Cc: Wayne Lin <wayne.lin@amd.com>
Cc: Nicholas Choi <nicholas.choi@amd.com>
Cc: Martin Peres <martin.peres@mupuf.org>
Cc: Aurabindo Pillai <aurabindo.pillai@amd.com>
Cc: Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
Cc: Qingqing Zhuo (Lilian) <qingqing.zhuo@amd.com>
Cc: Solomon Chiu <solomon.chiu@amd.com>
Cc: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Cc: Dingchen Zhang (David) <Dingchen.Zhang@amd.com>

Signed-off-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
---
 .gitignore                |   1 +
 CONTRIBUTING.md           |  17 ++++++-
 scripts/get_maintainer.sh | 104 ++++++++++++++++++++++++++++++++++++++
 3 files changed, 121 insertions(+), 1 deletion(-)
 create mode 100755 scripts/get_maintainer.sh

diff --git a/.gitignore b/.gitignore
index f81085ae..30ac6613 100644
--- a/.gitignore
+++ b/.gitignore
@@ -50,5 +50,6 @@ results
 build
 patches
 Makefile
+get_maintainer.pl
 
 .vscode
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 6d1294ad..e51779b0 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -42,7 +42,7 @@ Sending Patches
 - Please submit patches formatted with git send-email/git format-patch or
   equivalent to:
 
-      Development mailing list for IGT GPU Tools <igt-dev@lists.freedesktop.org>
+      IGT GPU Tools <igt-dev@lists.freedesktop.org>
 
   For patches affecting the driver directly please "cc" the appropriate driver
   mailing list and make sure you are using:
@@ -57,6 +57,21 @@ Sending Patches
 
   on its first invocation.
 
+- IGT has a MAINTAINERS file which is helpful to find people to review your
+  change; use the below command to extract the developer's name for a specific
+  test:
+
+    scripts/get_maintainer.sh [all|list|devs] [file/path|patch]
+
+  If you have a series, the below command will automatically assign the right
+  people in the "TO" and "CC" field:
+
+    git send-email --annotate --cover-letter --thread --no-chain-reply-to --to-cmd="bash scripts/get_maintainer.sh devs" --cc-cmd="bash scripts/get_maintainer.sh list" <SHA>
+
+  In case you have a single patch, you can use:
+
+    git send-email --annotate --to-cmd="bash scripts/get_maintainer.sh devs" --cc-cmd="bash scripts/get_maintainer.sh list" -1
+
 - Patches need to be reviewed on the mailing list. Exceptions only apply for
   testcases and tooling for drivers with just a single contributor (e.g. vc4).
   In this case patches must still be submitted to the mailing list first.
diff --git a/scripts/get_maintainer.sh b/scripts/get_maintainer.sh
new file mode 100755
index 00000000..a2d4110c
--- /dev/null
+++ b/scripts/get_maintainer.sh
@@ -0,0 +1,104 @@
+#!/bin/bash
+#
+# SPDX-License-Identifier: MIT
+#
+# Copyright 2022 Advanced Micro Devices, Inc.
+
+# List of constants
+declare -r GET_MAINTAINER_PATH='get_maintainer.pl'
+declare -r MAINTAINER_CMD="perl $GET_MAINTAINER_PATH"
+declare -r DEFAULT_OPTIONS='--no-tree --separator , --nokeywords --nogit --nogit-fallback --norolestats --remove-duplicates'
+declare -r ONLY_MAILING_LIST='--no-m -no-r --no-n'
+declare -r ONLY_DEVELOPERS='--no-l'
+declare -a get_maintainer_url=(
+  'https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/scripts/get_maintainer.pl'
+  'https://raw.githubusercontent.com/torvalds/linux/master/scripts/get_maintainer.pl'
+)
+
+declare -A options_values
+
+function print_help()
+{
+  printf "Usage: get_maintainer.sh [all|list|devs] [file/path|patch]\n"
+  printf "Available options:\n"
+  printf "  -h              display this help message\n"
+  printf ""
+}
+
+function download_get_maintainers()
+{
+  for url in ${get_maintainer_url[@]}; do
+    curl --silent "$url" --output "$GET_MAINTAINER_PATH"
+    # If we were able to download, there is no reason to try another link
+    [[ "$?" == 0 ]] && break
+  done
+}
+
+function parse_parameters()
+{
+  local parameters="$@"
+
+  options_values['PATH']=''
+
+  for parameter in ${parameters[@]}; do
+    case "${parameter}" in
+      --help | -h)
+        print_help
+        exit
+        ;;
+      list)
+        options_values['TARGET']='list'
+        ;;
+      all)
+        options_values['TARGET']='all'
+        ;;
+      devs)
+        options_values['TARGET']='devs'
+        ;;
+      *)
+        options_values['PATH']="${parameter}"
+        ;;
+    esac
+  done
+}
+
+function main()
+{
+  local raw_parameters="$@"
+  local cmd="$MAINTAINER_CMD $DEFAULT_OPTIONS"
+  local target
+
+  if [[ "$#" -lt 1 ]]; then
+    printf 'Invalid options\n'
+    print_help
+    exit 22
+  fi
+
+  parse_parameters "$@"
+  target="${options_values['TARGET']}"
+
+  # Download get_maintainers.pl if necessary
+  [[ ! -f "$GET_MAINTAINER_PATH" ]] && download_get_maintainers
+  if [[ ! -f "$GET_MAINTAINER_PATH" ]]; then
+    printf 'Unable to download get_maintainers file, please check your connection'
+    exit 22
+  fi
+
+  case "$target" in
+    list)
+      cmd+=" $ONLY_MAILING_LIST"
+      ;;
+    devs)
+      cmd+=" $ONLY_DEVELOPERS"
+      ;;
+  esac
+
+  # Do we have a file as a target?
+  if [[ -n ${options_values['PATH']} ]]; then
+    cmd+=" -f ${options_values['PATH']}"
+  fi
+
+  eval "$cmd"
+}
+
+main "$@"
-- 
2.25.1

^ permalink raw reply related	[flat|nested] 10+ messages in thread

* [igt-dev] ✓ Fi.CI.BAT: success for Introduce MAINTAINERS file to IGT (rev2)
  2022-02-17 15:26 [igt-dev] [PATCH 0/2] Introduce MAINTAINERS file to IGT Rodrigo Siqueira
  2022-02-17 15:26 ` [igt-dev] [PATCH 1/2] MAINTAINERS: Introduce MAINTAINERS file Rodrigo Siqueira
  2022-02-17 15:26 ` [igt-dev] [PATCH 2/2] scripts: get_maintainer: Introduce get_maintainer wrapper Rodrigo Siqueira
@ 2022-02-17 16:00 ` Patchwork
  2022-02-18  1:38 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
  2022-03-01 19:55 ` [igt-dev] [PATCH 0/2] Introduce MAINTAINERS file to IGT Rodrigo Vivi
  4 siblings, 0 replies; 10+ messages in thread
From: Patchwork @ 2022-02-17 16:00 UTC (permalink / raw)
  To: Rodrigo Siqueira; +Cc: igt-dev

[-- Attachment #1: Type: text/plain, Size: 7754 bytes --]

== Series Details ==

Series: Introduce MAINTAINERS file to IGT (rev2)
URL   : https://patchwork.freedesktop.org/series/99534/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_11240 -> IGTPW_6649
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/index.html

Participating hosts (44 -> 44)
------------------------------

  Additional (3): fi-icl-u2 fi-kbl-8809g fi-pnv-d510 
  Missing    (3): fi-bsw-cyan shard-tglu bat-adlp-4 

Known issues
------------

  Here are the changes found in IGTPW_6649 that come from known issues:

### IGT changes ###

#### Issues hit ####

  * igt@amdgpu/amd_basic@semaphore:
    - fi-hsw-4770:        NOTRUN -> [SKIP][1] ([fdo#109271] / [fdo#109315]) +17 similar issues
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-hsw-4770/igt@amdgpu/amd_basic@semaphore.html

  * igt@amdgpu/amd_cs_nop@fork-compute0:
    - fi-rkl-guc:         NOTRUN -> [SKIP][2] ([fdo#109315]) +17 similar issues
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-rkl-guc/igt@amdgpu/amd_cs_nop@fork-compute0.html

  * igt@amdgpu/amd_cs_nop@fork-gfx0:
    - fi-icl-u2:          NOTRUN -> [SKIP][3] ([fdo#109315]) +17 similar issues
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-icl-u2/igt@amdgpu/amd_cs_nop@fork-gfx0.html

  * igt@gem_exec_suspend@basic-s0@smem:
    - fi-kbl-8809g:       NOTRUN -> [DMESG-WARN][4] ([i915#4962]) +1 similar issue
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-kbl-8809g/igt@gem_exec_suspend@basic-s0@smem.html

  * igt@gem_huc_copy@huc-copy:
    - fi-pnv-d510:        NOTRUN -> [SKIP][5] ([fdo#109271]) +57 similar issues
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-pnv-d510/igt@gem_huc_copy@huc-copy.html
    - fi-kbl-8809g:       NOTRUN -> [SKIP][6] ([fdo#109271] / [i915#2190])
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-kbl-8809g/igt@gem_huc_copy@huc-copy.html
    - fi-icl-u2:          NOTRUN -> [SKIP][7] ([i915#2190])
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-icl-u2/igt@gem_huc_copy@huc-copy.html

  * igt@gem_lmem_swapping@parallel-random-engines:
    - fi-icl-u2:          NOTRUN -> [SKIP][8] ([i915#4613]) +3 similar issues
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-icl-u2/igt@gem_lmem_swapping@parallel-random-engines.html

  * igt@gem_lmem_swapping@random-engines:
    - fi-kbl-8809g:       NOTRUN -> [SKIP][9] ([fdo#109271] / [i915#4613]) +3 similar issues
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-kbl-8809g/igt@gem_lmem_swapping@random-engines.html

  * igt@i915_pm_rpm@basic-rte:
    - fi-kbl-8809g:       NOTRUN -> [SKIP][10] ([fdo#109271]) +54 similar issues
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-kbl-8809g/igt@i915_pm_rpm@basic-rte.html

  * igt@i915_selftest@live@requests:
    - fi-blb-e6850:       [PASS][11] -> [DMESG-FAIL][12] ([i915#5026])
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11240/fi-blb-e6850/igt@i915_selftest@live@requests.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-blb-e6850/igt@i915_selftest@live@requests.html

  * igt@kms_chamelium@hdmi-edid-read:
    - fi-kbl-8809g:       NOTRUN -> [SKIP][13] ([fdo#109271] / [fdo#111827]) +8 similar issues
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-kbl-8809g/igt@kms_chamelium@hdmi-edid-read.html

  * igt@kms_chamelium@hdmi-hpd-fast:
    - fi-icl-u2:          NOTRUN -> [SKIP][14] ([fdo#111827]) +8 similar issues
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-icl-u2/igt@kms_chamelium@hdmi-hpd-fast.html

  * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
    - fi-icl-u2:          NOTRUN -> [SKIP][15] ([fdo#109278]) +2 similar issues
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-icl-u2/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html

  * igt@kms_force_connector_basic@force-load-detect:
    - fi-icl-u2:          NOTRUN -> [SKIP][16] ([fdo#109285])
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-icl-u2/igt@kms_force_connector_basic@force-load-detect.html

  * igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
    - fi-kbl-8809g:       NOTRUN -> [SKIP][17] ([fdo#109271] / [i915#533])
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-kbl-8809g/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html

  * igt@kms_pipe_crc_basic@read-crc-pipe-b:
    - fi-cfl-8109u:       [PASS][18] -> [DMESG-WARN][19] ([i915#295]) +12 similar issues
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11240/fi-cfl-8109u/igt@kms_pipe_crc_basic@read-crc-pipe-b.html
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-cfl-8109u/igt@kms_pipe_crc_basic@read-crc-pipe-b.html

  * igt@prime_vgem@basic-userptr:
    - fi-icl-u2:          NOTRUN -> [SKIP][20] ([i915#3301])
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-icl-u2/igt@prime_vgem@basic-userptr.html

  * igt@runner@aborted:
    - fi-blb-e6850:       NOTRUN -> [FAIL][21] ([fdo#109271] / [i915#2403] / [i915#2426] / [i915#4312])
   [21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-blb-e6850/igt@runner@aborted.html
    - fi-bdw-5557u:       NOTRUN -> [FAIL][22] ([i915#2426] / [i915#4312])
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-bdw-5557u/igt@runner@aborted.html

  
#### Possible fixes ####

  * igt@i915_selftest@live@gt_lrc:
    - fi-rkl-guc:         [INCOMPLETE][23] -> [PASS][24]
   [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11240/fi-rkl-guc/igt@i915_selftest@live@gt_lrc.html
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-rkl-guc/igt@i915_selftest@live@gt_lrc.html

  * igt@i915_selftest@live@hangcheck:
    - fi-hsw-4770:        [INCOMPLETE][25] ([i915#3303]) -> [PASS][26]
   [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11240/fi-hsw-4770/igt@i915_selftest@live@hangcheck.html
   [26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/fi-hsw-4770/igt@i915_selftest@live@hangcheck.html

  
  [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
  [fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
  [fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
  [fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
  [fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
  [i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
  [i915#2403]: https://gitlab.freedesktop.org/drm/intel/issues/2403
  [i915#2426]: https://gitlab.freedesktop.org/drm/intel/issues/2426
  [i915#295]: https://gitlab.freedesktop.org/drm/intel/issues/295
  [i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
  [i915#3303]: https://gitlab.freedesktop.org/drm/intel/issues/3303
  [i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
  [i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
  [i915#4962]: https://gitlab.freedesktop.org/drm/intel/issues/4962
  [i915#5026]: https://gitlab.freedesktop.org/drm/intel/issues/5026
  [i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533


Build changes
-------------

  * CI: CI-20190529 -> None
  * IGT: IGT_6347 -> IGTPW_6649

  CI-20190529: 20190529
  CI_DRM_11240: 6c7dfb9d61c43210726e569c2523ec7cb6a2e3b9 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_6649: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/index.html
  IGT_6347: 37ea4c86f97c0e05fcb6b04cff72ec927930536e @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/index.html

[-- Attachment #2: Type: text/html, Size: 9805 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* [igt-dev] ✓ Fi.CI.IGT: success for Introduce MAINTAINERS file to IGT (rev2)
  2022-02-17 15:26 [igt-dev] [PATCH 0/2] Introduce MAINTAINERS file to IGT Rodrigo Siqueira
                   ` (2 preceding siblings ...)
  2022-02-17 16:00 ` [igt-dev] ✓ Fi.CI.BAT: success for Introduce MAINTAINERS file to IGT (rev2) Patchwork
@ 2022-02-18  1:38 ` Patchwork
  2022-03-01 19:55 ` [igt-dev] [PATCH 0/2] Introduce MAINTAINERS file to IGT Rodrigo Vivi
  4 siblings, 0 replies; 10+ messages in thread
From: Patchwork @ 2022-02-18  1:38 UTC (permalink / raw)
  To: Rodrigo Siqueira; +Cc: igt-dev

[-- Attachment #1: Type: text/plain, Size: 30258 bytes --]

== Series Details ==

Series: Introduce MAINTAINERS file to IGT (rev2)
URL   : https://patchwork.freedesktop.org/series/99534/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_11240_full -> IGTPW_6649_full
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/index.html

Participating hosts (11 -> 8)
------------------------------

  Missing    (3): pig-skl-6260u pig-kbl-iris pig-glk-j5005 

Possible new issues
-------------------

  Here are the unknown changes that may have been introduced in IGTPW_6649_full:

### IGT changes ###

#### Suppressed ####

  The following results come from untrusted machines, tests, or statuses.
  They do not affect the overall result.

  * igt@prime_self_import@export-vs-gem_close-race:
    - {shard-tglu}:       [PASS][1] -> [FAIL][2]
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11240/shard-tglu-2/igt@prime_self_import@export-vs-gem_close-race.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglu-6/igt@prime_self_import@export-vs-gem_close-race.html

  
Known issues
------------

  Here are the changes found in IGTPW_6649_full that come from known issues:

### IGT changes ###

#### Issues hit ####

  * igt@feature_discovery@chamelium:
    - shard-tglb:         NOTRUN -> [SKIP][3] ([fdo#111827])
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb5/igt@feature_discovery@chamelium.html
    - shard-iclb:         NOTRUN -> [SKIP][4] ([fdo#111827])
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb8/igt@feature_discovery@chamelium.html

  * igt@feature_discovery@display-3x:
    - shard-glk:          NOTRUN -> [SKIP][5] ([fdo#109271]) +98 similar issues
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-glk4/igt@feature_discovery@display-3x.html
    - shard-iclb:         NOTRUN -> [SKIP][6] ([i915#1839]) +2 similar issues
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb2/igt@feature_discovery@display-3x.html

  * igt@gem_ctx_persistence@smoketest:
    - shard-snb:          NOTRUN -> [SKIP][7] ([fdo#109271] / [i915#1099]) +2 similar issues
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-snb7/igt@gem_ctx_persistence@smoketest.html

  * igt@gem_ctx_sseu@engines:
    - shard-tglb:         NOTRUN -> [SKIP][8] ([i915#280])
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb8/igt@gem_ctx_sseu@engines.html

  * igt@gem_eio@kms:
    - shard-tglb:         NOTRUN -> [TIMEOUT][9] ([i915#3063])
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb3/igt@gem_eio@kms.html

  * igt@gem_exec_endless@dispatch@vecs0:
    - shard-iclb:         NOTRUN -> [INCOMPLETE][10] ([i915#3778])
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb1/igt@gem_exec_endless@dispatch@vecs0.html

  * igt@gem_exec_fair@basic-none-solo@rcs0:
    - shard-kbl:          NOTRUN -> [FAIL][11] ([i915#2842]) +6 similar issues
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-kbl6/igt@gem_exec_fair@basic-none-solo@rcs0.html
    - shard-glk:          NOTRUN -> [FAIL][12] ([i915#2842]) +2 similar issues
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-glk9/igt@gem_exec_fair@basic-none-solo@rcs0.html

  * igt@gem_exec_fair@basic-none@vcs0:
    - shard-tglb:         NOTRUN -> [FAIL][13] ([i915#2842]) +10 similar issues
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb7/igt@gem_exec_fair@basic-none@vcs0.html

  * igt@gem_exec_fair@basic-pace-share@rcs0:
    - shard-tglb:         [PASS][14] -> [FAIL][15] ([i915#2842])
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11240/shard-tglb7/igt@gem_exec_fair@basic-pace-share@rcs0.html
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb6/igt@gem_exec_fair@basic-pace-share@rcs0.html

  * igt@gem_exec_fair@basic-pace-solo@rcs0:
    - shard-kbl:          [PASS][16] -> [FAIL][17] ([i915#2842])
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11240/shard-kbl6/igt@gem_exec_fair@basic-pace-solo@rcs0.html
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-kbl1/igt@gem_exec_fair@basic-pace-solo@rcs0.html

  * igt@gem_exec_fair@basic-pace@vcs0:
    - shard-iclb:         NOTRUN -> [FAIL][18] ([i915#2842]) +8 similar issues
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb6/igt@gem_exec_fair@basic-pace@vcs0.html

  * igt@gem_exec_params@no-vebox:
    - shard-iclb:         NOTRUN -> [SKIP][19] ([fdo#109283])
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb7/igt@gem_exec_params@no-vebox.html
    - shard-tglb:         NOTRUN -> [SKIP][20] ([fdo#109283] / [i915#4877])
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb7/igt@gem_exec_params@no-vebox.html

  * igt@gem_exec_params@secure-non-root:
    - shard-tglb:         NOTRUN -> [SKIP][21] ([fdo#112283])
   [21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb2/igt@gem_exec_params@secure-non-root.html
    - shard-iclb:         NOTRUN -> [SKIP][22] ([fdo#112283])
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb4/igt@gem_exec_params@secure-non-root.html

  * igt@gem_exec_schedule@semaphore-codependency:
    - shard-snb:          NOTRUN -> [SKIP][23] ([fdo#109271]) +196 similar issues
   [23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-snb4/igt@gem_exec_schedule@semaphore-codependency.html

  * igt@gem_lmem_swapping@heavy-verify-random:
    - shard-kbl:          NOTRUN -> [SKIP][24] ([fdo#109271] / [i915#4613]) +2 similar issues
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-kbl6/igt@gem_lmem_swapping@heavy-verify-random.html
    - shard-tglb:         NOTRUN -> [SKIP][25] ([i915#4613]) +1 similar issue
   [25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb2/igt@gem_lmem_swapping@heavy-verify-random.html
    - shard-iclb:         NOTRUN -> [SKIP][26] ([i915#4613])
   [26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb1/igt@gem_lmem_swapping@heavy-verify-random.html

  * igt@gem_pxp@create-regular-context-2:
    - shard-tglb:         NOTRUN -> [SKIP][27] ([i915#4270]) +2 similar issues
   [27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb5/igt@gem_pxp@create-regular-context-2.html
    - shard-iclb:         NOTRUN -> [SKIP][28] ([i915#4270])
   [28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb1/igt@gem_pxp@create-regular-context-2.html

  * igt@gem_render_copy@linear-to-vebox-y-tiled:
    - shard-iclb:         NOTRUN -> [SKIP][29] ([i915#768]) +2 similar issues
   [29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb8/igt@gem_render_copy@linear-to-vebox-y-tiled.html

  * igt@gem_userptr_blits@dmabuf-sync:
    - shard-kbl:          NOTRUN -> [SKIP][30] ([fdo#109271] / [i915#3323])
   [30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-kbl4/igt@gem_userptr_blits@dmabuf-sync.html
    - shard-tglb:         NOTRUN -> [SKIP][31] ([i915#3323])
   [31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb2/igt@gem_userptr_blits@dmabuf-sync.html

  * igt@gem_userptr_blits@input-checking:
    - shard-kbl:          NOTRUN -> [DMESG-WARN][32] ([i915#4990])
   [32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-kbl3/igt@gem_userptr_blits@input-checking.html

  * igt@gem_userptr_blits@unsync-overlap:
    - shard-iclb:         NOTRUN -> [SKIP][33] ([i915#3297])
   [33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb1/igt@gem_userptr_blits@unsync-overlap.html

  * igt@gem_userptr_blits@unsync-unmap-cycles:
    - shard-tglb:         NOTRUN -> [SKIP][34] ([i915#3297]) +1 similar issue
   [34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb6/igt@gem_userptr_blits@unsync-unmap-cycles.html

  * igt@gen7_exec_parse@cmd-crossing-page:
    - shard-tglb:         NOTRUN -> [SKIP][35] ([fdo#109289]) +4 similar issues
   [35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb6/igt@gen7_exec_parse@cmd-crossing-page.html

  * igt@gen9_exec_parse@basic-rejected:
    - shard-iclb:         NOTRUN -> [SKIP][36] ([i915#2856]) +2 similar issues
   [36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb1/igt@gen9_exec_parse@basic-rejected.html

  * igt@gen9_exec_parse@bb-start-param:
    - shard-tglb:         NOTRUN -> [SKIP][37] ([i915#2527] / [i915#2856]) +2 similar issues
   [37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb2/igt@gen9_exec_parse@bb-start-param.html

  * igt@i915_pm_dc@dc3co-vpb-simulation:
    - shard-tglb:         NOTRUN -> [SKIP][38] ([i915#1904])
   [38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb8/igt@i915_pm_dc@dc3co-vpb-simulation.html
    - shard-apl:          NOTRUN -> [SKIP][39] ([fdo#109271] / [i915#658]) +1 similar issue
   [39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-apl8/igt@i915_pm_dc@dc3co-vpb-simulation.html
    - shard-iclb:         NOTRUN -> [SKIP][40] ([i915#658])
   [40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb5/igt@i915_pm_dc@dc3co-vpb-simulation.html

  * igt@i915_pm_rc6_residency@rc6-fence:
    - shard-tglb:         NOTRUN -> [WARN][41] ([i915#2681] / [i915#2684])
   [41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb5/igt@i915_pm_rc6_residency@rc6-fence.html
    - shard-iclb:         NOTRUN -> [WARN][42] ([i915#2684])
   [42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb8/igt@i915_pm_rc6_residency@rc6-fence.html

  * igt@i915_pm_rpm@modeset-lpsp-stress:
    - shard-apl:          NOTRUN -> [SKIP][43] ([fdo#109271]) +167 similar issues
   [43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-apl7/igt@i915_pm_rpm@modeset-lpsp-stress.html

  * igt@i915_pm_rpm@modeset-non-lpsp-stress:
    - shard-tglb:         NOTRUN -> [SKIP][44] ([fdo#111644] / [i915#1397] / [i915#2411]) +1 similar issue
   [44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb7/igt@i915_pm_rpm@modeset-non-lpsp-stress.html
    - shard-iclb:         NOTRUN -> [SKIP][45] ([fdo#110892])
   [45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb7/igt@i915_pm_rpm@modeset-non-lpsp-stress.html

  * igt@i915_query@query-topology-unsupported:
    - shard-tglb:         NOTRUN -> [SKIP][46] ([fdo#109302])
   [46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb8/igt@i915_query@query-topology-unsupported.html

  * igt@kms_big_fb@linear-16bpp-rotate-90:
    - shard-iclb:         NOTRUN -> [SKIP][47] ([fdo#110725] / [fdo#111614]) +4 similar issues
   [47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb6/igt@kms_big_fb@linear-16bpp-rotate-90.html

  * igt@kms_big_fb@linear-32bpp-rotate-180:
    - shard-glk:          NOTRUN -> [DMESG-WARN][48] ([i915#118])
   [48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-glk8/igt@kms_big_fb@linear-32bpp-rotate-180.html

  * igt@kms_big_fb@linear-8bpp-rotate-270:
    - shard-tglb:         NOTRUN -> [SKIP][49] ([fdo#111614]) +6 similar issues
   [49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb3/igt@kms_big_fb@linear-8bpp-rotate-270.html

  * igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip:
    - shard-glk:          NOTRUN -> [SKIP][50] ([fdo#109271] / [i915#3777])
   [50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-glk6/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip.html

  * igt@kms_big_fb@yf-tiled-64bpp-rotate-90:
    - shard-iclb:         NOTRUN -> [SKIP][51] ([fdo#110723]) +2 similar issues
   [51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb3/igt@kms_big_fb@yf-tiled-64bpp-rotate-90.html

  * igt@kms_big_fb@yf-tiled-8bpp-rotate-90:
    - shard-tglb:         NOTRUN -> [SKIP][52] ([fdo#111615]) +11 similar issues
   [52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb6/igt@kms_big_fb@yf-tiled-8bpp-rotate-90.html

  * igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip:
    - shard-apl:          NOTRUN -> [SKIP][53] ([fdo#109271] / [i915#3777]) +1 similar issue
   [53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-apl4/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip.html

  * igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip:
    - shard-kbl:          NOTRUN -> [SKIP][54] ([fdo#109271] / [i915#3777]) +6 similar issues
   [54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-kbl1/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip.html

  * igt@kms_big_joiner@2x-modeset:
    - shard-tglb:         NOTRUN -> [SKIP][55] ([i915#2705])
   [55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb3/igt@kms_big_joiner@2x-modeset.html

  * igt@kms_ccs@pipe-a-bad-rotation-90-y_tiled_gen12_mc_ccs:
    - shard-glk:          NOTRUN -> [SKIP][56] ([fdo#109271] / [i915#3886]) +6 similar issues
   [56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-glk9/igt@kms_ccs@pipe-a-bad-rotation-90-y_tiled_gen12_mc_ccs.html

  * igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_ccs:
    - shard-tglb:         NOTRUN -> [SKIP][57] ([i915#3689]) +5 similar issues
   [57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb8/igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_ccs.html

  * igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_mc_ccs:
    - shard-kbl:          NOTRUN -> [SKIP][58] ([fdo#109271] / [i915#3886]) +21 similar issues
   [58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-kbl6/igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_mc_ccs.html

  * igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc:
    - shard-apl:          NOTRUN -> [SKIP][59] ([fdo#109271] / [i915#3886]) +13 similar issues
   [59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-apl1/igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc.html

  * igt@kms_ccs@pipe-b-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs:
    - shard-tglb:         NOTRUN -> [SKIP][60] ([i915#3689] / [i915#3886]) +6 similar issues
   [60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb7/igt@kms_ccs@pipe-b-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs.html

  * igt@kms_ccs@pipe-c-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc:
    - shard-iclb:         NOTRUN -> [SKIP][61] ([fdo#109278] / [i915#3886]) +9 similar issues
   [61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb7/igt@kms_ccs@pipe-c-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc.html

  * igt@kms_ccs@pipe-c-crc-sprite-planes-basic-yf_tiled_ccs:
    - shard-tglb:         NOTRUN -> [SKIP][62] ([fdo#111615] / [i915#3689]) +6 similar issues
   [62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb8/igt@kms_ccs@pipe-c-crc-sprite-planes-basic-yf_tiled_ccs.html

  * igt@kms_cdclk@mode-transition:
    - shard-tglb:         NOTRUN -> [SKIP][63] ([i915#3742])
   [63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb8/igt@kms_cdclk@mode-transition.html

  * igt@kms_chamelium@dp-crc-multiple:
    - shard-apl:          NOTRUN -> [SKIP][64] ([fdo#109271] / [fdo#111827]) +13 similar issues
   [64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-apl3/igt@kms_chamelium@dp-crc-multiple.html

  * igt@kms_chamelium@dp-hpd-storm-disable:
    - shard-glk:          NOTRUN -> [SKIP][65] ([fdo#109271] / [fdo#111827]) +10 similar issues
   [65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-glk4/igt@kms_chamelium@dp-hpd-storm-disable.html

  * igt@kms_chamelium@hdmi-hpd-enable-disable-mode:
    - shard-iclb:         NOTRUN -> [SKIP][66] ([fdo#109284] / [fdo#111827]) +13 similar issues
   [66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb5/igt@kms_chamelium@hdmi-hpd-enable-disable-mode.html
    - shard-snb:          NOTRUN -> [SKIP][67] ([fdo#109271] / [fdo#111827]) +10 similar issues
   [67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-snb6/igt@kms_chamelium@hdmi-hpd-enable-disable-mode.html

  * igt@kms_chamelium@vga-hpd-for-each-pipe:
    - shard-kbl:          NOTRUN -> [SKIP][68] ([fdo#109271] / [fdo#111827]) +24 similar issues
   [68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-kbl6/igt@kms_chamelium@vga-hpd-for-each-pipe.html

  * igt@kms_color@pipe-d-ctm-blue-to-red:
    - shard-iclb:         NOTRUN -> [SKIP][69] ([fdo#109278] / [i915#1149]) +1 similar issue
   [69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb8/igt@kms_color@pipe-d-ctm-blue-to-red.html

  * igt@kms_color_chamelium@pipe-b-ctm-0-5:
    - shard-tglb:         NOTRUN -> [SKIP][70] ([fdo#109284] / [fdo#111827]) +22 similar issues
   [70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb7/igt@kms_color_chamelium@pipe-b-ctm-0-5.html

  * igt@kms_color_chamelium@pipe-d-gamma:
    - shard-iclb:         NOTRUN -> [SKIP][71] ([fdo#109278] / [fdo#109284] / [fdo#111827]) +1 similar issue
   [71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb3/igt@kms_color_chamelium@pipe-d-gamma.html

  * igt@kms_content_protection@dp-mst-lic-type-0:
    - shard-iclb:         NOTRUN -> [SKIP][72] ([i915#3116])
   [72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb7/igt@kms_content_protection@dp-mst-lic-type-0.html
    - shard-tglb:         NOTRUN -> [SKIP][73] ([i915#3116] / [i915#3299])
   [73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb7/igt@kms_content_protection@dp-mst-lic-type-0.html

  * igt@kms_content_protection@legacy:
    - shard-kbl:          NOTRUN -> [TIMEOUT][74] ([i915#1319])
   [74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-kbl4/igt@kms_content_protection@legacy.html
    - shard-tglb:         NOTRUN -> [SKIP][75] ([i915#1063])
   [75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb5/igt@kms_content_protection@legacy.html

  * igt@kms_content_protection@srm:
    - shard-iclb:         NOTRUN -> [SKIP][76] ([fdo#109300] / [fdo#111066])
   [76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb3/igt@kms_content_protection@srm.html
    - shard-apl:          NOTRUN -> [TIMEOUT][77] ([i915#1319]) +1 similar issue
   [77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-apl3/igt@kms_content_protection@srm.html

  * igt@kms_cursor_crc@pipe-a-cursor-32x32-sliding:
    - shard-tglb:         NOTRUN -> [SKIP][78] ([i915#3319]) +5 similar issues
   [78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb1/igt@kms_cursor_crc@pipe-a-cursor-32x32-sliding.html

  * igt@kms_cursor_crc@pipe-a-cursor-512x512-rapid-movement:
    - shard-iclb:         NOTRUN -> [SKIP][79] ([fdo#109278] / [fdo#109279]) +4 similar issues
   [79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb8/igt@kms_cursor_crc@pipe-a-cursor-512x512-rapid-movement.html

  * igt@kms_cursor_crc@pipe-c-cursor-suspend:
    - shard-kbl:          NOTRUN -> [DMESG-WARN][80] ([i915#180]) +2 similar issues
   [80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-kbl1/igt@kms_cursor_crc@pipe-c-cursor-suspend.html

  * igt@kms_cursor_crc@pipe-d-cursor-32x10-offscreen:
    - shard-iclb:         NOTRUN -> [SKIP][81] ([fdo#109278]) +44 similar issues
   [81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb7/igt@kms_cursor_crc@pipe-d-cursor-32x10-offscreen.html
    - shard-tglb:         NOTRUN -> [SKIP][82] ([i915#3359]) +9 similar issues
   [82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb7/igt@kms_cursor_crc@pipe-d-cursor-32x10-offscreen.html

  * igt@kms_cursor_crc@pipe-d-cursor-512x512-sliding:
    - shard-tglb:         NOTRUN -> [SKIP][83] ([fdo#109279] / [i915#3359]) +10 similar issues
   [83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb1/igt@kms_cursor_crc@pipe-d-cursor-512x512-sliding.html

  * igt@kms_cursor_crc@pipe-d-cursor-suspend:
    - shard-kbl:          NOTRUN -> [SKIP][84] ([fdo#109271]) +334 similar issues
   [84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-kbl7/igt@kms_cursor_crc@pipe-d-cursor-suspend.html

  * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-varying-size:
    - shard-tglb:         NOTRUN -> [SKIP][85] ([i915#4103]) +2 similar issues
   [85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb5/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-varying-size.html

  * igt@kms_cursor_legacy@cursorb-vs-flipa-toggle:
    - shard-iclb:         NOTRUN -> [SKIP][86] ([fdo#109274] / [fdo#109278]) +1 similar issue
   [86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb6/igt@kms_cursor_legacy@cursorb-vs-flipa-toggle.html

  * igt@kms_dp_tiled_display@basic-test-pattern-with-chamelium:
    - shard-tglb:         NOTRUN -> [SKIP][87] ([i915#3528])
   [87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb6/igt@kms_dp_tiled_display@basic-test-pattern-with-chamelium.html

  * igt@kms_dsc@basic-dsc-enable:
    - shard-iclb:         NOTRUN -> [SKIP][88] ([i915#3840])
   [88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb7/igt@kms_dsc@basic-dsc-enable.html

  * igt@kms_fbcon_fbt@fbc-suspend:
    - shard-apl:          [PASS][89] -> [INCOMPLETE][90] ([i915#180])
   [89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11240/shard-apl4/igt@kms_fbcon_fbt@fbc-suspend.html
   [90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-apl1/igt@kms_fbcon_fbt@fbc-suspend.html

  * igt@kms_flip@2x-blocking-absolute-wf_vblank-interruptible:
    - shard-tglb:         NOTRUN -> [SKIP][91] ([fdo#109274] / [fdo#111825]) +13 similar issues
   [91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb2/igt@kms_flip@2x-blocking-absolute-wf_vblank-interruptible.html

  * igt@kms_flip@2x-nonexisting-fb:
    - shard-iclb:         NOTRUN -> [SKIP][92] ([fdo#109274]) +9 similar issues
   [92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb2/igt@kms_flip@2x-nonexisting-fb.html

  * igt@kms_flip@flip-vs-suspend-interruptible@c-dp1:
    - shard-apl:          NOTRUN -> [DMESG-WARN][93] ([i915#180]) +1 similar issue
   [93]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-apl1/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html

  * igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling:
    - shard-iclb:         [PASS][94] -> [SKIP][95] ([i915#3701])
   [94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11240/shard-iclb1/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling.html
   [95]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling.html

  * igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilercccs-downscaling:
    - shard-iclb:         NOTRUN -> [SKIP][96] ([i915#2587])
   [96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb7/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilercccs-downscaling.html

  * igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-shrfb-msflip-blt:
    - shard-tglb:         NOTRUN -> [SKIP][97] ([fdo#109280] / [fdo#111825]) +52 similar issues
   [97]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb6/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-shrfb-msflip-blt.html

  * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-mmap-wc:
    - shard-iclb:         [PASS][98] -> [FAIL][99] ([i915#1888] / [i915#2546])
   [98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11240/shard-iclb1/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-mmap-wc.html
   [99]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb7/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-mmap-wc.html

  * igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-shrfb-draw-blt:
    - shard-iclb:         NOTRUN -> [SKIP][100] ([fdo#109280]) +31 similar issues
   [100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb5/igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-shrfb-draw-blt.html

  * igt@kms_hdr@bpc-switch-suspend:
    - shard-apl:          [PASS][101] -> [FAIL][102] ([i915#1188])
   [101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11240/shard-apl8/igt@kms_hdr@bpc-switch-suspend.html
   [102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-apl3/igt@kms_hdr@bpc-switch-suspend.html

  * igt@kms_hdr@static-toggle:
    - shard-iclb:         NOTRUN -> [SKIP][103] ([i915#1187]) +1 similar issue
   [103]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb8/igt@kms_hdr@static-toggle.html

  * igt@kms_hdr@static-toggle-dpms:
    - shard-tglb:         NOTRUN -> [SKIP][104] ([i915#1187]) +2 similar issues
   [104]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb5/igt@kms_hdr@static-toggle-dpms.html

  * igt@kms_multipipe_modeset@basic-max-pipe-crc-check:
    - shard-tglb:         NOTRUN -> [SKIP][105] ([i915#1839]) +2 similar issues
   [105]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb7/igt@kms_multipipe_modeset@basic-max-pipe-crc-check.html

  * igt@kms_pipe_b_c_ivb@from-pipe-c-to-b-with-3-lanes:
    - shard-iclb:         NOTRUN -> [SKIP][106] ([fdo#109289]) +2 similar issues
   [106]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb3/igt@kms_pipe_b_c_ivb@from-pipe-c-to-b-with-3-lanes.html

  * igt@kms_pipe_crc_basic@disable-crc-after-crtc-pipe-d:
    - shard-glk:          NOTRUN -> [SKIP][107] ([fdo#109271] / [i915#533])
   [107]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-glk7/igt@kms_pipe_crc_basic@disable-crc-after-crtc-pipe-d.html
    - shard-apl:          NOTRUN -> [SKIP][108] ([fdo#109271] / [i915#533])
   [108]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-apl2/igt@kms_pipe_crc_basic@disable-crc-after-crtc-pipe-d.html

  * igt@kms_pipe_crc_basic@read-crc-pipe-d:
    - shard-kbl:          NOTRUN -> [SKIP][109] ([fdo#109271] / [i915#533]) +1 similar issue
   [109]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-kbl4/igt@kms_pipe_crc_basic@read-crc-pipe-d.html

  * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:
    - shard-apl:          [PASS][110] -> [DMESG-WARN][111] ([i915#180]) +2 similar issues
   [110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11240/shard-apl4/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b.html
   [111]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-apl2/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b.html

  * igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb:
    - shard-apl:          NOTRUN -> [FAIL][112] ([i915#265])
   [112]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-apl1/igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb.html
    - shard-glk:          NOTRUN -> [FAIL][113] ([i915#265])
   [113]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-glk7/igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb.html

  * igt@kms_plane_alpha_blend@pipe-b-constant-alpha-max:
    - shard-glk:          NOTRUN -> [FAIL][114] ([fdo#108145] / [i915#265])
   [114]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-glk4/igt@kms_plane_alpha_blend@pipe-b-constant-alpha-max.html
    - shard-apl:          NOTRUN -> [FAIL][115] ([fdo#108145] / [i915#265])
   [115]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-apl1/igt@kms_plane_alpha_blend@pipe-b-constant-alpha-max.html

  * igt@kms_plane_alpha_blend@pipe-c-alpha-7efc:
    - shard-kbl:          NOTRUN -> [FAIL][116] ([fdo#108145] / [i915#265]) +2 similar issues
   [116]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-kbl4/igt@kms_plane_alpha_blend@pipe-c-alpha-7efc.html

  * igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb:
    - shard-kbl:          NOTRUN -> [FAIL][117] ([i915#265]) +1 similar issue
   [117]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-kbl3/igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb.html

  * igt@kms_plane_lowres@pipe-b-tiling-x:
    - shard-iclb:         NOTRUN -> [SKIP][118] ([i915#3536]) +2 similar issues
   [118]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb3/igt@kms_plane_lowres@pipe-b-tiling-x.html

  * igt@kms_plane_lowres@pipe-b-tiling-yf:
    - shard-tglb:         NOTRUN -> [SKIP][119] ([fdo#111615] / [fdo#112054]) +1 similar issue
   [119]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb7/igt@kms_plane_lowres@pipe-b-tiling-yf.html

  * igt@kms_plane_lowres@pipe-d-tiling-y:
    - shard-tglb:         NOTRUN -> [SKIP][120] ([i915#3536]) +2 similar issues
   [120]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb3/igt@kms_plane_lowres@pipe-d-tiling-y.html

  * igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area:
    - shard-iclb:         NOTRUN -> [SKIP][121] ([i915#2920])
   [121]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb2/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area.html

  * igt@kms_psr2_sf@plane-move-sf-dmg-area:
    - shard-tglb:         NOTRUN -> [SKIP][122] ([i915#2920]) +1 similar issue
   [122]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb7/igt@kms_psr2_sf@plane-move-sf-dmg-area.html

  * igt@kms_psr2_su@page_flip-xrgb8888:
    - shard-tglb:         NOTRUN -> [SKIP][123] ([i915#1911]) +1 similar issue
   [123]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-tglb5/igt@kms_psr2_su@page_flip-xrgb8888.html
    - shard-kbl:          NOTRUN -> [SKIP][124] ([fdo#109271] / [i915#658]) +4 similar issues
   [124]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-kbl3/igt@kms_psr2_su@page_flip-xrgb8888.html
    - shard-glk:          NOTRUN -> [SKIP][125] ([fdo#109271] / [i915#658]) +3 similar issues
   [125]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-glk9/igt@kms_psr2_su@page_flip-xrgb8888.html
    - shard-iclb:         NOTRUN -> [SKIP][126] ([fdo#109642] / [fdo#111068] / [i915#658]) +1 similar issue
   [126]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/shard-iclb8/igt@kms_psr2_su@page_flip-xrgb8888.html

  * igt@kms_psr@psr2_cursor_mmap_cpu:
    - shard-

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6649/index.html

[-- Attachment #2: Type: text/html, Size: 34010 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [igt-dev] [PATCH 1/2] MAINTAINERS: Introduce MAINTAINERS file
  2022-02-17 15:26 ` [igt-dev] [PATCH 1/2] MAINTAINERS: Introduce MAINTAINERS file Rodrigo Siqueira
@ 2022-03-01 16:10   ` Harry Wentland
  2022-03-01 18:45   ` Melissa Wen
  1 sibling, 0 replies; 10+ messages in thread
From: Harry Wentland @ 2022-03-01 16:10 UTC (permalink / raw)
  To: Rodrigo Siqueira, Arkadiusz Hiler, Petri Latvala
  Cc: igt-dev, Qingqing Zhuo, Sean Paul, Bhawanpreet Lakha, Mark Yacoub



On 2022-02-17 10:26, Rodrigo Siqueira wrote:
> IGT is growing in terms of new vendors actively using it. Right now, we
> only have Intel CI to validate new patches, which can create a situation
> where bugs get accidentally introduced to other vendors. To alleviate
> this problem and also making easy for other developers to be aware of
> some specific changes, I'm proposing the introduction of the MAINTAINERS
> file as the one used in the Linux kernel. With this approach, we can
> have multiple enginers from different companies as reviewers for
> specific tests, and contributors should use get_maintainers script to
> find the right people to address their changes.
> 
> Cc: Arkadiusz Hiler <arek@hiler.eu>
> Cc: Petri Latvala <petri.latvala@intel.com>
> Cc: Mark Yacoub <markyacoub@google.com>
> Cc: Jessica Zhang <quic_jesszhan@quicinc.com>
> Cc: Abhinav Kumar <quic_abhinavk@quicinc.com>
> Cc: Melissa Wen <mwen@igalia.com>
> Cc: Sean Paul <seanpaul@chromium.org>
> Cc: Harry Wentland <harry.wentland@amd.com>
> Cc: Sun Peng Li(Leo) <sunpeng.li@amd.com>
> Cc: Chao-kai Wang (Stylon) <stylon.wang@amd.com>
> Cc: Wayne Lin <wayne.lin@amd.com>
> Cc: Nicholas Choi <nicholas.choi@amd.com>
> Cc: Martin Peres <martin.peres@mupuf.org>
> Cc: Aurabindo Pillai <aurabindo.pillai@amd.com>
> Cc: Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
> Cc: Qingqing Zhuo (Lilian) <qingqing.zhuo@amd.com>
> Cc: Solomon Chiu <solomon.chiu@amd.com>
> Cc: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> Cc: Dingchen Zhang (David) <Dingchen.Zhang@amd.com>
> 
> Signed-off-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> ---
>  MAINTAINERS | 198 +++++++++++++++++++++++++++++++++++++++++++++++++++-
>  1 file changed, 196 insertions(+), 2 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 383c327c..fac605de 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1,2 +1,196 @@
> -Petri Latvala <petri.latvala@intel.com>
> -Arkadiusz Hiler <arek@hiler.eu>
> +List of maintainers/reviewers to submit IGT changes
> +===================================================
> +
> +Please try to follow the guidelines below.  This will make things
> +easier on the maintainers.  Not all of these guidelines matter for every
> +trivial patch so apply some common sense.
> +
> +Tips for patch submitters
> +-------------------------
> +
> +1.	Always *test* your changes.
> +
> +2.	Make sure your changes compile correctly.
> +
> +3.	When you are happy with a change make it generally available for
> +	testing and await feedback.
> +
> +4.	Make a patch available to the relevant maintainer in the list. Be prepared
> +	to get your changes sent back with seemingly silly requests about
> +	formatting and variable names. These aren't as silly as they seem. One job
> +	the maintainers do is to keep things looking the same.
> +
> +	PLEASE CC: the maintainers and mailing lists that are generated
> +	by ``scripts/get_maintainer.sh.`` The results returned by the
> +	script will be best if you have git installed.
> +
> +	PLEASE try to include any credit lines you want added with the
> +	patch. It avoids people being missed off by mistake and makes
> +	it easier to know who wants adding and who doesn't.
> +
> +	PLEASE document known bugs.
> +
> +5.	Make sure you have the right to send any changes you make. If you
> +	do changes at work you may find your employer owns the patch
> +	not you.
> +
> +Descriptions of section entries and preferred order
> +---------------------------------------------------
> +
> +	M: *Mail* patches to: FullName <address@domain>
> +	R: Designated *Reviewer*: FullName <address@domain>
> +	   These reviewers should be CCed on patches.
> +	L: *Mailing list* that is relevant to this area
> +	S: *Status*, one of the following:
> +	   Supported:	Someone is actually paid to look after this.
> +	   Maintained:	Someone actually looks after it.
> +	W: *Web-page* with status/info
> +	Q: *Patchwork* web based patch tracking system site
> +	B: URI for where to file *bugs*. A web-page with detailed bug
> +	   filing info, a direct bug tracker link, or a mailto: URI.
> +	C: URI for *chat* protocol, server and channel where developers
> +	   usually hang out, for example irc://server/channel.
> +	T: *SCM* tree type and location.
> +	   Type is one of: git, hg, quilt, stgit, topgit
> +	F: *Files* and directories wildcard patterns.
> +	   A trailing slash includes all files and subdirectory files.
> +	   F:	tests/amdgpu/	all files in and below tests/amdgpu
> +	   F:	tests/*	all files in tests/, but not below
> +	   One pattern per line.  Multiple F: lines acceptable.
> +	X: *Excluded* files and directories that are NOT maintained, same
> +	   rules as F:. Files exclusions are tested before file matches.
> +
> +Maintainers List
> +----------------
> +
> +KMS Generic API tests
> +R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> +R:	Qingqing Zhuo (Lilian) <Qingqing.Zhuo@amd.com@amd.com>
> +R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
> +F:	tests/kms_atomic.c
> +F:	tests/kms_atomic_interruptible.c
> +F:	tests/kms_atomic_transition.c
> +F:	tests/kms_properties.c
> +F:	tests/kms_setmode.c
> +F:	tests/kms_concurrent.c
> +F:	tests/kms_prop_blob.c
> +F:	tests/kms_multipipe_modeset.c
> +
> +KMS CRC API
> +R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> +R:	Sunpeng Li (Leo) <Sunpeng.Li@amd.com>
> +R:	Dingchen Zhang (David) <Dingchen.Zhang@amd.com>
> +R:	Melissa Wen <mwen@igalia.com>
> +F:	tests/kms_cursor_crc.c
> +F:	tests/kms_pipe_crc_basic.c
> +F:	tests/kms_rotation_crc.c
> +
> +KMS HDR
> +R:	Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>

+F:	tests/kms_hhdr.c

Otherwise it looks good.

Acked-by: Harry Wentland <harry.wentland@amd.com>

Harry

> +
> +KMS Color
> +R:	Stylon Wang <stylon.wang@amd.com>
> +R:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
> +R:	Sunpeng Li (Leo) <Sunpeng.Li@amd.com>
> +F:	tests/kms_color.c
> +
> +KMS Content protection
> +R:	Dingchen Zhang (David) <Dingchen.Zhang@amd.com>
> +R:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
> +F:	tests/kms_content_protection.c
> +
> +KMS Cursor tests
> +R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> +R:	Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> +F:	tests/kms_cursor_legacy.c
> +F:	tests/kms_cursor_edge_walk.c
> +F:	tests/kms_plane_cursor.c
> +F:	tests/kms_plane_alpha_blend.c
> +
> +VRR tests
> +R:	Stylon Wang <stylon.wang@amd.com>
> +R:	Wayne Lin <Wayne.Lin@amd.com>
> +R:	Solomon Chiu <Solomon.Chiu@amd.com>
> +R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
> +R:	Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> +S:	Maintained
> +F:	tests/kms_vrr.c
> +
> +KMS Vblank tests
> +R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
> +R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> +S:	Maintained
> +F:	tests/kms_vblank.c
> +
> +KMS Flip tests
> +R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
> +R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> +S:	Maintained
> +F:	tests/kms_flip.c
> +F:	tests/kms_flip_event_leak.c
> +
> +KMS plane tests
> +R:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
> +R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> +R:	Stylon Wang <stylon.wang@amd.com>
> +S:	Maintained
> +F:	tests/kms_plane.c
> +F:	tests/kms_plane_scaling.c
> +
> +KMS Bandwidth
> +R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
> +F:	tests/kms_bw.c
> +
> +AMDGPU
> +M:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> +M:	Stylon Wang <stylon.wang@amd.com>
> +M:	Wayne Lin <Wayne.Lin@amd.com>
> +S:	Maintained
> +F:	tests/amdgpu/*
> +
> +AMDGPU AMD Plane
> +M:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
> +F:	tests/amdgpu/amd_plane.c
> +
> +AMDGPU AMD Link
> +M:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
> +F:	tests/amdgpu/amd_link_settings.c
> +F:	tests/amdgpu/amd_dp_dsc.c
> +F:	tests/amdgpu/amd_hotplug.c
> +
> +AMDGPU AMD Color
> +M:	Stylon Wang <stylon.wang@amd.com>
> +R:	Sunpeng Li (Leo) <Sunpeng.Li@amd.com>
> +R:	Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> +F:	tests/amdgpu/amd_color.c
> +F:	tests/amdgpu/amd_max_bpc.c
> +
> +AMDGPU AMD content protection
> +M:	Stylon Wang <stylon.wang@amd.com>
> +R:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
> +F:	tests/amdgpu/amd_assr.c
> +
> +AMDGPU VRR/Freesync
> +M:	Stylon Wang <stylon.wang@amd.com>
> +M:	Solomon Chiu <Solomon.Chiu@amd.com>
> +R:	Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> +R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
> +F:	tests/amdgpu/amd_vrr_range.c
> +
> +All KMS tests
> +R:	Mark Yacoub <markyacoub@chromium.org>
> +F:	tests/kms_*
> +
> +V3D tests
> +R:	Melissa Wen <mwen@igalia.com>
> +F:	tests/v3d_*
> +
> +THE REST
> +M:	Arkadiusz Hiler <arek@hiler.eu>
> +M:	Petri Latvala <petri.latvala@intel.com>
> +L:	igt-dev@lists.freedesktop.org
> +B:	https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues
> +Q:	https://patchwork.freedesktop.org/project/igt/series/?ordering=-last_updated
> +T:	git@gitlab.freedesktop.org:drm/igt-gpu-tools.git
> +F:	*
> +F:	*/

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [igt-dev] [PATCH 1/2] MAINTAINERS: Introduce MAINTAINERS file
  2022-02-17 15:26 ` [igt-dev] [PATCH 1/2] MAINTAINERS: Introduce MAINTAINERS file Rodrigo Siqueira
  2022-03-01 16:10   ` Harry Wentland
@ 2022-03-01 18:45   ` Melissa Wen
  1 sibling, 0 replies; 10+ messages in thread
From: Melissa Wen @ 2022-03-01 18:45 UTC (permalink / raw)
  To: Rodrigo Siqueira
  Cc: Petri Latvala, Bhawanpreet Lakha, Qingqing Zhuo, igt-dev,
	Sean Paul, Mark Yacoub

[-- Attachment #1: Type: text/plain, Size: 9070 bytes --]

On 02/17, Rodrigo Siqueira wrote:
> IGT is growing in terms of new vendors actively using it. Right now, we
> only have Intel CI to validate new patches, which can create a situation
> where bugs get accidentally introduced to other vendors. To alleviate
> this problem and also making easy for other developers to be aware of
> some specific changes, I'm proposing the introduction of the MAINTAINERS
> file as the one used in the Linux kernel. With this approach, we can
> have multiple enginers from different companies as reviewers for
> specific tests, and contributors should use get_maintainers script to
> find the right people to address their changes.
> 
> Cc: Arkadiusz Hiler <arek@hiler.eu>
> Cc: Petri Latvala <petri.latvala@intel.com>
> Cc: Mark Yacoub <markyacoub@google.com>
> Cc: Jessica Zhang <quic_jesszhan@quicinc.com>
> Cc: Abhinav Kumar <quic_abhinavk@quicinc.com>
> Cc: Melissa Wen <mwen@igalia.com>
> Cc: Sean Paul <seanpaul@chromium.org>
> Cc: Harry Wentland <harry.wentland@amd.com>
> Cc: Sun Peng Li(Leo) <sunpeng.li@amd.com>
> Cc: Chao-kai Wang (Stylon) <stylon.wang@amd.com>
> Cc: Wayne Lin <wayne.lin@amd.com>
> Cc: Nicholas Choi <nicholas.choi@amd.com>
> Cc: Martin Peres <martin.peres@mupuf.org>
> Cc: Aurabindo Pillai <aurabindo.pillai@amd.com>
> Cc: Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
> Cc: Qingqing Zhuo (Lilian) <qingqing.zhuo@amd.com>
> Cc: Solomon Chiu <solomon.chiu@amd.com>
> Cc: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> Cc: Dingchen Zhang (David) <Dingchen.Zhang@amd.com>
> 
> Signed-off-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> ---
>  MAINTAINERS | 198 +++++++++++++++++++++++++++++++++++++++++++++++++++-
>  1 file changed, 196 insertions(+), 2 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 383c327c..fac605de 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1,2 +1,196 @@
> -Petri Latvala <petri.latvala@intel.com>
> -Arkadiusz Hiler <arek@hiler.eu>
> +List of maintainers/reviewers to submit IGT changes
> +===================================================
> +
> +Please try to follow the guidelines below.  This will make things
> +easier on the maintainers.  Not all of these guidelines matter for every
> +trivial patch so apply some common sense.
> +
> +Tips for patch submitters
> +-------------------------
> +
> +1.	Always *test* your changes.
> +
> +2.	Make sure your changes compile correctly.
> +
> +3.	When you are happy with a change make it generally available for
> +	testing and await feedback.
> +
> +4.	Make a patch available to the relevant maintainer in the list. Be prepared
> +	to get your changes sent back with seemingly silly requests about
> +	formatting and variable names. These aren't as silly as they seem. One job
> +	the maintainers do is to keep things looking the same.
> +
> +	PLEASE CC: the maintainers and mailing lists that are generated
> +	by ``scripts/get_maintainer.sh.`` The results returned by the
> +	script will be best if you have git installed.
> +
> +	PLEASE try to include any credit lines you want added with the
> +	patch. It avoids people being missed off by mistake and makes
> +	it easier to know who wants adding and who doesn't.
> +
> +	PLEASE document known bugs.
> +
> +5.	Make sure you have the right to send any changes you make. If you
> +	do changes at work you may find your employer owns the patch
> +	not you.
> +
> +Descriptions of section entries and preferred order
> +---------------------------------------------------
> +
> +	M: *Mail* patches to: FullName <address@domain>
> +	R: Designated *Reviewer*: FullName <address@domain>
> +	   These reviewers should be CCed on patches.
> +	L: *Mailing list* that is relevant to this area
> +	S: *Status*, one of the following:
> +	   Supported:	Someone is actually paid to look after this.
> +	   Maintained:	Someone actually looks after it.
> +	W: *Web-page* with status/info
> +	Q: *Patchwork* web based patch tracking system site
> +	B: URI for where to file *bugs*. A web-page with detailed bug
> +	   filing info, a direct bug tracker link, or a mailto: URI.
> +	C: URI for *chat* protocol, server and channel where developers
> +	   usually hang out, for example irc://server/channel.
> +	T: *SCM* tree type and location.
> +	   Type is one of: git, hg, quilt, stgit, topgit
> +	F: *Files* and directories wildcard patterns.
> +	   A trailing slash includes all files and subdirectory files.
> +	   F:	tests/amdgpu/	all files in and below tests/amdgpu
> +	   F:	tests/*	all files in tests/, but not below
> +	   One pattern per line.  Multiple F: lines acceptable.
> +	X: *Excluded* files and directories that are NOT maintained, same
> +	   rules as F:. Files exclusions are tested before file matches.
> +
> +Maintainers List
> +----------------
> +
> +KMS Generic API tests
> +R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> +R:	Qingqing Zhuo (Lilian) <Qingqing.Zhuo@amd.com@amd.com>
> +R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
> +F:	tests/kms_atomic.c
> +F:	tests/kms_atomic_interruptible.c
> +F:	tests/kms_atomic_transition.c
> +F:	tests/kms_properties.c
> +F:	tests/kms_setmode.c
> +F:	tests/kms_concurrent.c
> +F:	tests/kms_prop_blob.c
> +F:	tests/kms_multipipe_modeset.c
> +
> +KMS CRC API
> +R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> +R:	Sunpeng Li (Leo) <Sunpeng.Li@amd.com>
> +R:	Dingchen Zhang (David) <Dingchen.Zhang@amd.com>
> +R:	Melissa Wen <mwen@igalia.com>
> +F:	tests/kms_cursor_crc.c
> +F:	tests/kms_pipe_crc_basic.c
> +F:	tests/kms_rotation_crc.c
> +
> +KMS HDR
> +R:	Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
> +
> +KMS Color
> +R:	Stylon Wang <stylon.wang@amd.com>
> +R:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
> +R:	Sunpeng Li (Leo) <Sunpeng.Li@amd.com>
> +F:	tests/kms_color.c
> +
> +KMS Content protection
> +R:	Dingchen Zhang (David) <Dingchen.Zhang@amd.com>
> +R:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
> +F:	tests/kms_content_protection.c
> +
> +KMS Cursor tests
> +R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> +R:	Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> +F:	tests/kms_cursor_legacy.c
> +F:	tests/kms_cursor_edge_walk.c
> +F:	tests/kms_plane_cursor.c
> +F:	tests/kms_plane_alpha_blend.c
> +
> +VRR tests
> +R:	Stylon Wang <stylon.wang@amd.com>
> +R:	Wayne Lin <Wayne.Lin@amd.com>
> +R:	Solomon Chiu <Solomon.Chiu@amd.com>
> +R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
> +R:	Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> +S:	Maintained
> +F:	tests/kms_vrr.c
> +
> +KMS Vblank tests
> +R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
> +R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> +S:	Maintained
> +F:	tests/kms_vblank.c
> +
> +KMS Flip tests
> +R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
> +R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> +S:	Maintained
> +F:	tests/kms_flip.c
> +F:	tests/kms_flip_event_leak.c
> +
> +KMS plane tests
> +R:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
> +R:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> +R:	Stylon Wang <stylon.wang@amd.com>
> +S:	Maintained
> +F:	tests/kms_plane.c
> +F:	tests/kms_plane_scaling.c
> +
> +KMS Bandwidth
> +R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
> +F:	tests/kms_bw.c
> +
> +AMDGPU
> +M:	Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> +M:	Stylon Wang <stylon.wang@amd.com>
> +M:	Wayne Lin <Wayne.Lin@amd.com>
> +S:	Maintained
> +F:	tests/amdgpu/*
> +
> +AMDGPU AMD Plane
> +M:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
> +F:	tests/amdgpu/amd_plane.c
> +
> +AMDGPU AMD Link
> +M:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
> +F:	tests/amdgpu/amd_link_settings.c
> +F:	tests/amdgpu/amd_dp_dsc.c
> +F:	tests/amdgpu/amd_hotplug.c
> +
> +AMDGPU AMD Color
> +M:	Stylon Wang <stylon.wang@amd.com>
> +R:	Sunpeng Li (Leo) <Sunpeng.Li@amd.com>
> +R:	Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> +F:	tests/amdgpu/amd_color.c
> +F:	tests/amdgpu/amd_max_bpc.c
> +
> +AMDGPU AMD content protection
> +M:	Stylon Wang <stylon.wang@amd.com>
> +R:	Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
> +F:	tests/amdgpu/amd_assr.c
> +
> +AMDGPU VRR/Freesync
> +M:	Stylon Wang <stylon.wang@amd.com>
> +M:	Solomon Chiu <Solomon.Chiu@amd.com>
> +R:	Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> +R:	Aurabindo Pillai <aurabindo.pillai@amd.com>
> +F:	tests/amdgpu/amd_vrr_range.c
> +
> +All KMS tests
> +R:	Mark Yacoub <markyacoub@chromium.org>
> +F:	tests/kms_*
> +
> +V3D tests
> +R:	Melissa Wen <mwen@igalia.com>
> +F:	tests/v3d_*

Acked-by: Melissa Wen <mwen@igalia.com>
> +
> +THE REST
> +M:	Arkadiusz Hiler <arek@hiler.eu>
> +M:	Petri Latvala <petri.latvala@intel.com>
> +L:	igt-dev@lists.freedesktop.org
> +B:	https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues
> +Q:	https://patchwork.freedesktop.org/project/igt/series/?ordering=-last_updated
> +T:	git@gitlab.freedesktop.org:drm/igt-gpu-tools.git
> +F:	*
> +F:	*/
> -- 
> 2.25.1
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [igt-dev] [PATCH 0/2] Introduce MAINTAINERS file to IGT
  2022-02-17 15:26 [igt-dev] [PATCH 0/2] Introduce MAINTAINERS file to IGT Rodrigo Siqueira
                   ` (3 preceding siblings ...)
  2022-02-18  1:38 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
@ 2022-03-01 19:55 ` Rodrigo Vivi
  2022-03-16 13:24   ` Rodrigo Siqueira Jordao
  4 siblings, 1 reply; 10+ messages in thread
From: Rodrigo Vivi @ 2022-03-01 19:55 UTC (permalink / raw)
  To: Rodrigo Siqueira
  Cc: Petri Latvala, Qingqing Zhuo, igt-dev, Sean Paul,
	Bhawanpreet Lakha, Mark Yacoub

On Thu, Feb 17, 2022 at 10:26:44AM -0500, Rodrigo Siqueira wrote:
> IGT is becoming more generic, and multiple vendors are adopting it. For
> example, AMD fully upstream all of its internal changes last year, and
> now we are relying on IGT from the upstream. Additionally, thanks to the
> ChromeOS project, we have other vendors working on the KMS tests as
> well. At this point, I believe that we need some mechanism to better
> contact developers that care about some specific tests or even provide
> an easy way for other people to find the right stakeholder for dealing
> with some particular issue.
> 
> Imho Linux Kernel already has a good solution codified in the
> MAINTAINERS and get_maintainers files. One of the best things about this
> approach was adding reviewers and maintainers (and other options) to the
> specific part of the code and using the get_maintainers tool to extract
> the right people to be part of the series. With this idea in mind, I
> created an RFC that introduces the MAINTAINERS file in IGT, and
> collected feedback. This series is the first version that introduces the
> MAINTAINERS and a wrapper to the get_maintainers file.

But in the Linux Kernel we do for big blocks, not for individual .c files.
For the .c files git blame should be enough imho...

> 
> For this series, I recommend:
> 
> 1. Patch 1: It has the maintainers file. If you want to add yourself to
> some specific test, please, let me know in this patch.
> 2. Patch 2: get_maintainers wrapper, see the CONTRIBUTING page on how to
> use it.
> 
> Cc: Arkadiusz Hiler <arek@hiler.eu>
> Cc: Petri Latvala <petri.latvala@intel.com>
> Cc: Mark Yacoub <markyacoub@google.com>
> Cc: Jessica Zhang <quic_jesszhan@quicinc.com>
> Cc: Abhinav Kumar <quic_abhinavk@quicinc.com>
> Cc: Melissa Wen <mwen@igalia.com>
> Cc: Sean Paul <seanpaul@chromium.org>
> Cc: Harry Wentland <harry.wentland@amd.com>
> Cc: Sun Peng Li(Leo) <sunpeng.li@amd.com>
> Cc: Chao-kai Wang (Stylon) <stylon.wang@amd.com>
> Cc: Wayne Lin <wayne.lin@amd.com>
> Cc: Nicholas Choi <nicholas.choi@amd.com>
> Cc: Martin Peres <martin.peres@mupuf.org>
> Cc: Aurabindo Pillai <aurabindo.pillai@amd.com>
> Cc: Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
> Cc: Qingqing Zhuo (Lilian) <qingqing.zhuo@amd.com>
> Cc: Solomon Chiu <solomon.chiu@amd.com>
> Cc: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> Cc: Dingchen Zhang (David) <Dingchen.Zhang@amd.com>
> 
> Rodrigo Siqueira (2):
>   MAINTAINERS: Introduce MAINTAINERS file
>   scripts: get_maintainer: Introduce get_maintainer wrapper
> 
>  .gitignore                |   1 +
>  CONTRIBUTING.md           |  17 +++-
>  MAINTAINERS               | 198 +++++++++++++++++++++++++++++++++++++-
>  scripts/get_maintainer.sh | 104 ++++++++++++++++++++
>  4 files changed, 317 insertions(+), 3 deletions(-)
>  create mode 100755 scripts/get_maintainer.sh
> 
> -- 
> 2.25.1
> 

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [igt-dev] [PATCH 0/2] Introduce MAINTAINERS file to IGT
  2022-03-01 19:55 ` [igt-dev] [PATCH 0/2] Introduce MAINTAINERS file to IGT Rodrigo Vivi
@ 2022-03-16 13:24   ` Rodrigo Siqueira Jordao
  2022-03-21 17:35     ` Vivi, Rodrigo
  0 siblings, 1 reply; 10+ messages in thread
From: Rodrigo Siqueira Jordao @ 2022-03-16 13:24 UTC (permalink / raw)
  To: Rodrigo Vivi, Rodrigo Siqueira
  Cc: Petri Latvala, Qingqing Zhuo, igt-dev, Sean Paul,
	Bhawanpreet Lakha, Mark Yacoub



On 2022-03-01 14:55, Rodrigo Vivi wrote:
> On Thu, Feb 17, 2022 at 10:26:44AM -0500, Rodrigo Siqueira wrote:
>> IGT is becoming more generic, and multiple vendors are adopting it. For
>> example, AMD fully upstream all of its internal changes last year, and
>> now we are relying on IGT from the upstream. Additionally, thanks to the
>> ChromeOS project, we have other vendors working on the KMS tests as
>> well. At this point, I believe that we need some mechanism to better
>> contact developers that care about some specific tests or even provide
>> an easy way for other people to find the right stakeholder for dealing
>> with some particular issue.
>>
>> Imho Linux Kernel already has a good solution codified in the
>> MAINTAINERS and get_maintainers files. One of the best things about this
>> approach was adding reviewers and maintainers (and other options) to the
>> specific part of the code and using the get_maintainers tool to extract
>> the right people to be part of the series. With this idea in mind, I
>> created an RFC that introduces the MAINTAINERS file in IGT, and
>> collected feedback. This series is the first version that introduces the
>> MAINTAINERS and a wrapper to the get_maintainers file.
> 
> But in the Linux Kernel we do for big blocks, not for individual .c files.
> For the .c files git blame should be enough imho...

Hi Rodrigo,

I don't think git blame will work for what I'm suggesting. What I'm 
trying to achieve here is a bit different; I'm trying to add more 
contact points for specific tests since IGT became more and more adopted.
For example, last year, we retired our IGT fork and tried to upstream 
all of our internal changes since we want to move to the upstream first 
approach with IGT. As a result of this change, our CI now relies on IGT 
from GitLab, and we run a lot of the kms tests, but we did not directly 
work in some of them. In those cases, git blame will not point to anyone 
from AMD. If you see the first patch, we are trying to add specific 
people to follow certain tests to make the IGT maintenance scalable for 
us and for anyone using IGT in their CI.

Thanks
Siqueira


>>
>> For this series, I recommend:
>>
>> 1. Patch 1: It has the maintainers file. If you want to add yourself to
>> some specific test, please, let me know in this patch.
>> 2. Patch 2: get_maintainers wrapper, see the CONTRIBUTING page on how to
>> use it.
>>
>> Cc: Arkadiusz Hiler <arek@hiler.eu>
>> Cc: Petri Latvala <petri.latvala@intel.com>
>> Cc: Mark Yacoub <markyacoub@google.com>
>> Cc: Jessica Zhang <quic_jesszhan@quicinc.com>
>> Cc: Abhinav Kumar <quic_abhinavk@quicinc.com>
>> Cc: Melissa Wen <mwen@igalia.com>
>> Cc: Sean Paul <seanpaul@chromium.org>
>> Cc: Harry Wentland <harry.wentland@amd.com>
>> Cc: Sun Peng Li(Leo) <sunpeng.li@amd.com>
>> Cc: Chao-kai Wang (Stylon) <stylon.wang@amd.com>
>> Cc: Wayne Lin <wayne.lin@amd.com>
>> Cc: Nicholas Choi <nicholas.choi@amd.com>
>> Cc: Martin Peres <martin.peres@mupuf.org>
>> Cc: Aurabindo Pillai <aurabindo.pillai@amd.com>
>> Cc: Bhawanpreet Lakha <bhawanpreet.lakha@amd.com>
>> Cc: Qingqing Zhuo (Lilian) <qingqing.zhuo@amd.com>
>> Cc: Solomon Chiu <solomon.chiu@amd.com>
>> Cc: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
>> Cc: Dingchen Zhang (David) <Dingchen.Zhang@amd.com>
>>
>> Rodrigo Siqueira (2):
>>    MAINTAINERS: Introduce MAINTAINERS file
>>    scripts: get_maintainer: Introduce get_maintainer wrapper
>>
>>   .gitignore                |   1 +
>>   CONTRIBUTING.md           |  17 +++-
>>   MAINTAINERS               | 198 +++++++++++++++++++++++++++++++++++++-
>>   scripts/get_maintainer.sh | 104 ++++++++++++++++++++
>>   4 files changed, 317 insertions(+), 3 deletions(-)
>>   create mode 100755 scripts/get_maintainer.sh
>>
>> -- 
>> 2.25.1
>>

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [igt-dev] [PATCH 0/2] Introduce MAINTAINERS file to IGT
  2022-03-16 13:24   ` Rodrigo Siqueira Jordao
@ 2022-03-21 17:35     ` Vivi, Rodrigo
  0 siblings, 0 replies; 10+ messages in thread
From: Vivi, Rodrigo @ 2022-03-21 17:35 UTC (permalink / raw)
  To: rjordrigo, Rodrigo.Siqueira
  Cc: Latvala, Petri, qingqing.zhuo, igt-dev, seanpaul,
	bhawanpreet.lakha, markyacoub

[-- Attachment #1: Type: text/plain, Size: 4718 bytes --]

On Wed, 2022-03-16 at 09:24 -0400, Rodrigo Siqueira Jordao wrote:


On 2022-03-01 14:55, Rodrigo Vivi wrote:
On Thu, Feb 17, 2022 at 10:26:44AM -0500, Rodrigo Siqueira wrote:
IGT is becoming more generic, and multiple vendors are adopting it. For
example, AMD fully upstream all of its internal changes last year, and
now we are relying on IGT from the upstream. Additionally, thanks to the
ChromeOS project, we have other vendors working on the KMS tests as
well. At this point, I believe that we need some mechanism to better
contact developers that care about some specific tests or even provide
an easy way for other people to find the right stakeholder for dealing
with some particular issue.

Imho Linux Kernel already has a good solution codified in the
MAINTAINERS and get_maintainers files. One of the best things about this
approach was adding reviewers and maintainers (and other options) to the
specific part of the code and using the get_maintainers tool to extract
the right people to be part of the series. With this idea in mind, I
created an RFC that introduces the MAINTAINERS file in IGT, and
collected feedback. This series is the first version that introduces the
MAINTAINERS and a wrapper to the get_maintainers file.

But in the Linux Kernel we do for big blocks, not for individual .c files.
For the .c files git blame should be enough imho...

Hi Rodrigo,

I don't think git blame will work for what I'm suggesting. What I'm
trying to achieve here is a bit different; I'm trying to add more
contact points for specific tests since IGT became more and more adopted.
For example, last year, we retired our IGT fork and tried to upstream
all of our internal changes since we want to move to the upstream first
approach with IGT. As a result of this change, our CI now relies on IGT
from GitLab, and we run a lot of the kms tests, but we did not directly
work in some of them. In those cases, git blame will not point to anyone
from AMD. If you see the first patch, we are trying to add specific
people to follow certain tests to make the IGT maintenance scalable for
us and for anyone using IGT in their CI.

I totally understand your goal here and I fully support any action that brings the
upstream first approach. My biggest concern with this approach is the maintenance cost.
A list big and very specific like this will likely change quickly and get outdated in the blink of an eye.

But it is just my personal thought on this. Please sync with Petri to determine the good path of this.


Thanks
Siqueira



For this series, I recommend:

1. Patch 1: It has the maintainers file. If you want to add yourself to
some specific test, please, let me know in this patch.
2. Patch 2: get_maintainers wrapper, see the CONTRIBUTING page on how to
use it.

Cc: Arkadiusz Hiler <arek@hiler.eu<mailto:arek@hiler.eu>>
Cc: Petri Latvala <petri.latvala@intel.com<mailto:petri.latvala@intel.com>>
Cc: Mark Yacoub <markyacoub@google.com<mailto:markyacoub@google.com>>
Cc: Jessica Zhang <quic_jesszhan@quicinc.com<mailto:quic_jesszhan@quicinc.com>>
Cc: Abhinav Kumar <quic_abhinavk@quicinc.com<mailto:quic_abhinavk@quicinc.com>>
Cc: Melissa Wen <mwen@igalia.com<mailto:mwen@igalia.com>>
Cc: Sean Paul <seanpaul@chromium.org<mailto:seanpaul@chromium.org>>
Cc: Harry Wentland <harry.wentland@amd.com<mailto:harry.wentland@amd.com>>
Cc: Sun Peng Li(Leo) <sunpeng.li@amd.com<mailto:sunpeng.li@amd.com>>
Cc: Chao-kai Wang (Stylon) <stylon.wang@amd.com<mailto:stylon.wang@amd.com>>
Cc: Wayne Lin <wayne.lin@amd.com<mailto:wayne.lin@amd.com>>
Cc: Nicholas Choi <nicholas.choi@amd.com<mailto:nicholas.choi@amd.com>>
Cc: Martin Peres <martin.peres@mupuf.org<mailto:martin.peres@mupuf.org>>
Cc: Aurabindo Pillai <aurabindo.pillai@amd.com<mailto:aurabindo.pillai@amd.com>>
Cc: Bhawanpreet Lakha <bhawanpreet.lakha@amd.com<mailto:bhawanpreet.lakha@amd.com>>
Cc: Qingqing Zhuo (Lilian) <qingqing.zhuo@amd.com<mailto:qingqing.zhuo@amd.com>>
Cc: Solomon Chiu <solomon.chiu@amd.com<mailto:solomon.chiu@amd.com>>
Cc: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com<mailto:nicholas.kazlauskas@amd.com>>
Cc: Dingchen Zhang (David) <Dingchen.Zhang@amd.com<mailto:Dingchen.Zhang@amd.com>>

Rodrigo Siqueira (2):
   MAINTAINERS: Introduce MAINTAINERS file
   scripts: get_maintainer: Introduce get_maintainer wrapper

  .gitignore                |   1 +
  CONTRIBUTING.md           |  17 +++-
  MAINTAINERS               | 198 +++++++++++++++++++++++++++++++++++++-
  scripts/get_maintainer.sh | 104 ++++++++++++++++++++
  4 files changed, 317 insertions(+), 3 deletions(-)
  create mode 100755 scripts/get_maintainer.sh

--
2.25.1




[-- Attachment #2: Type: text/html, Size: 8018 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2022-03-21 17:35 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-17 15:26 [igt-dev] [PATCH 0/2] Introduce MAINTAINERS file to IGT Rodrigo Siqueira
2022-02-17 15:26 ` [igt-dev] [PATCH 1/2] MAINTAINERS: Introduce MAINTAINERS file Rodrigo Siqueira
2022-03-01 16:10   ` Harry Wentland
2022-03-01 18:45   ` Melissa Wen
2022-02-17 15:26 ` [igt-dev] [PATCH 2/2] scripts: get_maintainer: Introduce get_maintainer wrapper Rodrigo Siqueira
2022-02-17 16:00 ` [igt-dev] ✓ Fi.CI.BAT: success for Introduce MAINTAINERS file to IGT (rev2) Patchwork
2022-02-18  1:38 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2022-03-01 19:55 ` [igt-dev] [PATCH 0/2] Introduce MAINTAINERS file to IGT Rodrigo Vivi
2022-03-16 13:24   ` Rodrigo Siqueira Jordao
2022-03-21 17:35     ` Vivi, Rodrigo

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.