From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Sagar Arun Kamble <sagar.a.kamble@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v12 03/11] drm/i915: Move i915_gem_restore_fences to i915_gem_resume
Date: Mon, 02 Oct 2017 11:33:54 +0300 [thread overview]
Message-ID: <1506933234.6755.0.camel@linux.intel.com> (raw)
In-Reply-To: <ff5822da-1506-f09a-97f5-af3495cd6e4d@intel.com>
On Fri, 2017-09-29 at 19:29 +0530, Sagar Arun Kamble wrote:
>
> On 9/29/2017 5:18 PM, Joonas Lahtinen wrote:
> > On Thu, 2017-09-28 at 12:18 +0530, Sagar Arun Kamble wrote:
> > > i915_gem_restore_fences is GEM resumption task hence it is moved to
> > > i915_gem_resume from i915_restore_state.
> >
> > + Chris
> >
> > Didn't I just review this patch elsewhere? Other thread explains that
> > the emytology of fixing display checks out, what you suggest is more
> > appropriate. Question is if we should note with a comment?
> >
> > PS. You seem to have sent this with --suppress-cc, which decreases the
> > chances of getting the reviews :)
>
> No. this was sent without "--suppress-cc". I actually floated two
> revisions yesterday so it might have been missed.
> Sorry for the thrash.
> How did you figure out "--suppress-cc"? Don't see in the headers
There were Cc: entries in the text, but as the patch reached me, there
were none.
Could be the mailing list acting weird, too.
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-10-02 8:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 6:48 [PATCH v12 00/11] GEM/GuC Suspend/Resume/Reset fixes and restructuring Sagar Arun Kamble
2017-09-28 6:48 ` [PATCH v12 01/11] drm/i915: Create GEM runtime resume helper and handle GEM suspend/resume errors Sagar Arun Kamble
2017-09-29 11:43 ` Joonas Lahtinen
2017-09-29 11:49 ` Chris Wilson
2017-09-29 13:16 ` Joonas Lahtinen
2017-09-29 13:51 ` Sagar Arun Kamble
2017-09-28 6:48 ` [PATCH v12 02/11] drm/i915: Update GEM suspend/resume flows with GuC suspend/resume functions Sagar Arun Kamble
2017-09-29 11:45 ` Joonas Lahtinen
2017-09-29 13:52 ` Sagar Arun Kamble
2017-09-28 6:48 ` [PATCH v12 03/11] drm/i915: Move i915_gem_restore_fences to i915_gem_resume Sagar Arun Kamble
2017-09-29 11:48 ` Joonas Lahtinen
2017-09-29 13:59 ` Sagar Arun Kamble
2017-09-29 14:01 ` Sagar Arun Kamble
2017-10-02 8:33 ` Joonas Lahtinen [this message]
2017-09-28 6:48 ` [PATCH v12 04/11] drm/i915: Create uC runtime and system suspend/resume helpers Sagar Arun Kamble
2017-09-29 12:12 ` Joonas Lahtinen
2017-09-29 14:13 ` Sagar Arun Kamble
2017-09-29 14:39 ` Michal Wajdeczko
2017-09-28 6:48 ` [PATCH v12 05/11] drm/i915/guc: Introduce intel_uc_sanitize Sagar Arun Kamble
2017-09-29 12:00 ` Joonas Lahtinen
2017-09-29 14:22 ` Sagar Arun Kamble
2017-10-02 8:37 ` Joonas Lahtinen
2017-09-28 6:48 ` [PATCH v12 06/11] drm/i915/guc: Make GuC related disable/destroy functions not depend on i915.enable_guc_submission Sagar Arun Kamble
2017-09-29 12:27 ` Joonas Lahtinen
2017-09-30 8:22 ` Sagar Arun Kamble
2017-10-02 8:51 ` Joonas Lahtinen
2017-09-28 6:48 ` [PATCH v12 07/11] drm/i915/guc: Update i915.enable_guc_loading check in intel_uc_fini_hw Sagar Arun Kamble
2017-09-29 12:29 ` Joonas Lahtinen
2017-09-28 6:48 ` [PATCH v12 08/11] drm/i915/guc: Update GuC ggtt.invalidate/interrupts/communication across RPM suspend/resume Sagar Arun Kamble
2017-09-28 6:48 ` [PATCH v12 09/11] drm/i915/guc: Update GuC functionality in intel_uc_suspend/intel_uc_resume Sagar Arun Kamble
2017-09-28 6:48 ` [PATCH v12 10/11] drm/i915/guc: Disable GuC submission and suspend it prior to i915 reset Sagar Arun Kamble
2017-09-28 6:48 ` [PATCH v12 11/11] drm/i915/guc: Fix GuC cleanup in unload path Sagar Arun Kamble
2017-09-28 7:11 ` ✗ Fi.CI.BAT: warning for GEM/GuC Suspend/Resume/Reset fixes and restructuring (rev5) Patchwork
2017-09-28 7:38 ` Sagar Arun Kamble
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=1506933234.6755.0.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sagar.a.kamble@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