From: Aaron Ma <aaron.ma@canonical.com>
To: anshuman.gupta@intel.com
Cc: intel-gfx@lists.freedesktop.org, jianshui.yu@intel.com,
lidong.wang@intel.com, rodrigo.vivi@intel.com,
stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915/dgfx: Enable d3cold at s2idle
Date: Thu, 17 Aug 2023 21:10:02 +0800 [thread overview]
Message-ID: <838aac7d-dbbd-5a04-7c25-344d8e0512b5@canonical.com> (raw)
In-Reply-To: <20230816125216.1722002-1-anshuman.gupta@intel.com>
Tested-by: Aaron Ma <aaron.ma@canonical.com>
WARNING: multiple messages have this Message-ID (diff)
From: Aaron Ma <aaron.ma@canonical.com>
To: anshuman.gupta@intel.com
Cc: intel-gfx@lists.freedesktop.org, rodrigo.vivi@intel.com,
lidong.wang@intel.com, stable@vger.kernel.org,
jianshui.yu@intel.com
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915/dgfx: Enable d3cold at s2idle
Date: Thu, 17 Aug 2023 21:10:02 +0800 [thread overview]
Message-ID: <838aac7d-dbbd-5a04-7c25-344d8e0512b5@canonical.com> (raw)
In-Reply-To: <20230816125216.1722002-1-anshuman.gupta@intel.com>
Tested-by: Aaron Ma <aaron.ma@canonical.com>
next prev parent reply other threads:[~2023-08-17 13:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 12:52 [Intel-gfx] [PATCH v2] drm/i915/dgfx: Enable d3cold at s2idle Anshuman Gupta
2023-08-16 12:52 ` Anshuman Gupta
2023-08-16 14:42 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dgfx: Enable d3cold at s2idle (rev2) Patchwork
2023-08-16 14:42 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-16 15:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-08-16 21:03 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-08-17 13:10 ` Aaron Ma [this message]
2023-08-17 13:10 ` [Intel-gfx] [PATCH v2] drm/i915/dgfx: Enable d3cold at s2idle Aaron Ma
2023-08-17 14:39 ` Yu, Jianshui
2023-08-17 14:39 ` Yu, Jianshui
2023-08-17 16:07 ` [Intel-gfx] " Gupta, Anshuman
2023-08-17 16:07 ` Gupta, Anshuman
2023-08-18 0:36 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/dgfx: Enable d3cold at s2idle (rev3) 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=838aac7d-dbbd-5a04-7c25-344d8e0512b5@canonical.com \
--to=aaron.ma@canonical.com \
--cc=anshuman.gupta@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jianshui.yu@intel.com \
--cc=lidong.wang@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.