Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: Katarzyna Piecielska <katarzyna.piecielska@intel.com>
Cc: <igt-dev@lists.freedesktop.org>,
	Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
Subject: Re: [PATCH i-g-t v2 09/25] tests/intel: Introduce FDinfo subcategory
Date: Mon, 11 Mar 2024 12:19:20 -0700	[thread overview]
Message-ID: <Ze9ZOOuke9uLRTDs@unerlige-ril> (raw)
In-Reply-To: <20240308083657.1092049-10-katarzyna.piecielska@intel.com>

On Fri, Mar 08, 2024 at 08:36:41AM +0000, Katarzyna Piecielska wrote:
>Let's introduce FDinfo subcategory.
>
>Signed-off-by: Katarzyna Piecielska <katarzyna.piecielska@intel.com>
>Cc: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
>Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
>Cc: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>

Acked-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>

Thanks,
Umesh
>---
> tests/intel/drm_fdinfo.c | 3 +++
> 1 file changed, 3 insertions(+)
>
>diff --git a/tests/intel/drm_fdinfo.c b/tests/intel/drm_fdinfo.c
>index 3ced658f2..65d942330 100644
>--- a/tests/intel/drm_fdinfo.c
>+++ b/tests/intel/drm_fdinfo.c
>@@ -37,6 +37,9 @@
>  * TEST: drm fdinfo
>  * Description: Test the i915 drm fdinfo data
>  * Feature: client_busyness
>+ * Functionality: client_busyness
>+ * Sub-category: FDinfo
>+ * Category: Desktop client
>  * Run type: FULL
>  *
>  * SUBTEST: all-busy-check-all
>-- 
>2.34.1
>

  parent reply	other threads:[~2024-03-11 19:19 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08  8:36 [PATCH i-g-t v2 00/25] Update test documentation for i915 tests Katarzyna Piecielska
2024-03-08  8:36 ` [PATCH i-g-t v2 01/25] tests: Introduce uapi subcategory Katarzyna Piecielska
2024-03-11 15:05   ` Kamil Konieczny
2024-03-08  8:36 ` [PATCH i-g-t v2 02/25] tests/intel: Introduce Memory management subcategory Katarzyna Piecielska
2024-03-11 14:06   ` Dandamudi, Priyanka
2024-03-08  8:36 ` [PATCH i-g-t v2 03/25] tests/intel: Introduce CMD submission subcategory Katarzyna Piecielska
2024-03-08  8:36 ` [PATCH i-g-t v2 04/25] tests/intel: Introduce Caching subcategory Katarzyna Piecielska
2024-03-08  8:36 ` [PATCH i-g-t v2 05/25] tests/intel: Let's introduce Workarounds subcategory Katarzyna Piecielska
2024-03-11 15:07   ` Kamil Konieczny
2024-03-08  8:36 ` [PATCH i-g-t v2 06/25] tests/intel: Add tests to Compute subcategory Katarzyna Piecielska
2024-03-11 15:08   ` Kamil Konieczny
2024-03-08  8:36 ` [PATCH i-g-t v2 07/25] tests/intel: Introduce GPGPU subcategory Katarzyna Piecielska
2024-03-11 13:57   ` Zbigniew Kempczyński
2024-03-08  8:36 ` [PATCH i-g-t v2 08/25] tests/intel: Introduce Blitter subcategory Katarzyna Piecielska
2024-03-11 14:00   ` Zbigniew Kempczyński
2024-03-08  8:36 ` [PATCH i-g-t v2 09/25] tests/intel: Introduce FDinfo subcategory Katarzyna Piecielska
2024-03-11 15:10   ` Kamil Konieczny
2024-03-11 19:19   ` Umesh Nerlige Ramappa [this message]
2024-03-08  8:36 ` [PATCH i-g-t v2 10/25] tests/intel: Introduce Flat-ccs subcategory Katarzyna Piecielska
2024-03-08  8:36 ` [PATCH i-g-t v2 11/25] tests/intel: Introduce Firmware subcategory Katarzyna Piecielska
2024-03-11 15:17   ` Kamil Konieczny
2024-03-08  8:36 ` [PATCH i-g-t v2 12/25] tests/intel: Introduce Media subcategory Katarzyna Piecielska
2024-03-11 13:59   ` Zbigniew Kempczyński
2024-03-08  8:36 ` [PATCH i-g-t v2 13/25] tests/intel: Introduce Render copy subcategory Katarzyna Piecielska
2024-03-11 13:58   ` Zbigniew Kempczyński
2024-03-08  8:36 ` [PATCH i-g-t v2 14/25] tests/intel: Introduce Obsolete subcategory Katarzyna Piecielska
2024-03-11 15:20   ` Kamil Konieczny
2024-03-08  8:36 ` [PATCH i-g-t v2 15/25] tests/intel: Introduce Power management subcategory Katarzyna Piecielska
2024-03-08  8:36 ` [PATCH i-g-t v2 16/25] tests/intel: Introduce SysMan subcategory Katarzyna Piecielska
2024-03-08  8:36 ` [PATCH i-g-t v2 17/25] tests: Introduce Core subcategory Katarzyna Piecielska
2024-03-08  8:36 ` [PATCH i-g-t v2 18/25] tests: Introduce Synchronization subcategory Katarzyna Piecielska
2024-03-08  8:36 ` [PATCH i-g-t v2 19/25] tests: Introduce intel-nouveau subcategory Katarzyna Piecielska
2024-03-08  8:36 ` [PATCH i-g-t v2 20/25] tests/intel: Introduce Debugging subcategory Katarzyna Piecielska
2024-03-08  8:36 ` [PATCH i-g-t v2 21/25] tests/intel: Add missing documentation fields in i915_selftest Katarzyna Piecielska
2024-03-12 10:12   ` Girotra, Himanshu
2024-03-08  8:36 ` [PATCH i-g-t v2 22/25] tests/intel: Add more tests to Performance subcategory Katarzyna Piecielska
2024-03-08  8:36 ` [PATCH i-g-t v2 23/25] tests: Add missing documentation fields for SRIOV and Display Katarzyna Piecielska
2024-03-08  8:36 ` [PATCH i-g-t v2 24/25] tests: Remove 'Run type' documentation field Katarzyna Piecielska
2024-03-08  8:36 ` [PATCH i-g-t v2 25/25] tests: Update device_reset functionality Katarzyna Piecielska
2024-03-12  7:58   ` Dandamudi, Priyanka
2024-03-08 10:18 ` ✗ GitLab.Pipeline: warning for Update test documentation for i915 tests (rev2) Patchwork
2024-03-08 10:36 ` ✓ CI.xeBAT: success " Patchwork
2024-03-08 10:50 ` ✗ Fi.CI.BAT: failure " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Ze9ZOOuke9uLRTDs@unerlige-ril \
    --to=umesh.nerlige.ramappa@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=katarzyna.piecielska@intel.com \
    --cc=mauro.chehab@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox