From: Lucas De Marchi <lucas.demarchi@intel.com>
To: igt-dev@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH i-g-t 1/3] tests/intel/xe_pm: Reword *-basic description
Date: Mon, 6 May 2024 13:05:49 -0700 [thread overview]
Message-ID: <171502591870.221895.6594240825962594814.b4-ty@intel.com> (raw)
In-Reply-To: <20240503224745.14890-1-lucas.demarchi@intel.com>
On Fri, 03 May 2024 15:47:43 -0700, Lucas De Marchi wrote:
> It doesn't make much sense to say the CPU is going to be put in D*
> state. Reword it so the CPU and GPU states are better captured.
>
>
Applied all patches. Thanks for the reviews.
[1/3] tests/intel/xe_pm: Reword *-basic description
commit: 3f70c934874d55cfadd8bf36027293bb7fa200e7
[2/3] lib/igt_aux: Name function according to sysfs file
commit: 022b83443d594bd2ca909735872ab663e4ad5672
[3/3] tests/intel/xe_pm: S4 to go up to devices only
commit: 4b767566bbc6c3ac342b54620aec0fabc8cdd4bf
Best regards,
--
Lucas De Marchi <lucas.demarchi@intel.com>
prev parent reply other threads:[~2024-05-06 20:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 22:47 [PATCH i-g-t 1/3] tests/intel/xe_pm: Reword *-basic description Lucas De Marchi
2024-05-03 22:47 ` [PATCH i-g-t 2/3] lib/igt_aux: Name function according to sysfs file Lucas De Marchi
2024-05-06 14:12 ` Rodrigo Vivi
2024-05-03 22:47 ` [PATCH i-g-t 3/3] tests/intel/xe_pm: S4 to go up to devices only Lucas De Marchi
2024-05-06 14:14 ` Rodrigo Vivi
2024-05-06 16:48 ` Lucas De Marchi
2024-05-03 23:28 ` ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/3] tests/intel/xe_pm: Reword *-basic description Patchwork
2024-05-04 0:10 ` ✓ CI.xeBAT: " Patchwork
2024-05-04 2:22 ` ✗ CI.xeFULL: failure " Patchwork
2024-05-04 11:51 ` ✗ Fi.CI.IGT: " Patchwork
2024-05-06 14:10 ` [PATCH i-g-t 1/3] " Rodrigo Vivi
2024-05-06 20:05 ` Lucas De Marchi [this message]
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=171502591870.221895.6594240825962594814.b4-ty@intel.com \
--to=lucas.demarchi@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=rodrigo.vivi@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