From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/5] lib/igt_aux: Let's use the official mem_sleep names
Date: Fri, 05 Aug 2022 11:49:26 -0700 [thread overview]
Message-ID: <85a68i8r0p.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20220801180145.243227-1-rodrigo.vivi@intel.com>
On Mon, 01 Aug 2022 11:01:41 -0700, Rodrigo Vivi wrote:
>
> diff --git a/lib/igt_aux.h b/lib/igt_aux.h
> index af663d2c..9d5b7bd2 100644
> --- a/lib/igt_aux.h
> +++ b/lib/igt_aux.h
> @@ -196,9 +196,9 @@ enum igt_suspend_test {
> */
Hmm the comment above still contains the old names...
> enum igt_mem_sleep {
> MEM_SLEEP_NONE,
> - MEM_SLEEP_FREEZE,
> - MEM_SLEEP_STANDBY,
> - MEM_SLEEP_MEM,
> + MEM_SLEEP_S2IDLE,
> + MEM_SLEEP_SHALLOW,
> + MEM_SLEEP_DEEP,
prev parent reply other threads:[~2022-08-05 18:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 18:01 [igt-dev] [PATCH i-g-t 1/5] lib/igt_aux: Let's use the official mem_sleep names Rodrigo Vivi
2022-08-01 18:01 ` [igt-dev] [PATCH i-g-t 2/5] tests/i915/i915_suspend: Be more specific on the S3 mem_sleep requirement Rodrigo Vivi
2022-08-01 18:01 ` [igt-dev] [PATCH i-g-t 3/5] lib/igt_aux: Check suspend state support directly Rodrigo Vivi
2022-08-01 18:10 ` [igt-dev] [PATCH i-g-t] " Rodrigo Vivi
2022-08-03 9:59 ` Gupta, Anshuman
2022-08-03 16:02 ` Rodrigo Vivi
2022-08-01 18:01 ` [igt-dev] [PATCH i-g-t 4/5] lib/igt_aux: Introduce the ability to force S3 suspend state Rodrigo Vivi
2022-08-01 18:01 ` [igt-dev] [PATCH i-g-t 5/5] test/i915/i915_suspend: Use SUSPEND_STATE_S3 to enforce S3 Rodrigo Vivi
2022-08-01 19:31 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/5] lib/igt_aux: Let's use the official mem_sleep names (rev2) Patchwork
2022-08-02 4:45 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2022-08-05 18:49 ` Dixit, Ashutosh [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=85a68i8r0p.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@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