From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [CI v4 1/3] drm/i915/guc: Disable send function on fini
Date: Tue, 30 May 2017 11:22:39 +0300 [thread overview]
Message-ID: <1496132559.3977.3.camel@linux.intel.com> (raw)
In-Reply-To: <20170526111326.87280-2-michal.wajdeczko@intel.com>
On pe, 2017-05-26 at 11:13 +0000, Michal Wajdeczko wrote:
> In earlier patch 789a625 we were enabling send function only
> after successful init. For completeness, we should make sure
> that we disable it on fini.
>
> v2: don't group steps by submission flag (Chris)
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Not worthy Fixes: ?
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-05-30 8:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 11:13 [CI v4 0/3] Introduce buffer based cmd transport Michal Wajdeczko
2017-05-26 11:13 ` [CI v4 1/3] drm/i915/guc: Disable send function on fini Michal Wajdeczko
2017-05-30 8:22 ` Joonas Lahtinen [this message]
2017-05-26 11:13 ` [CI v4 2/3] drm/i915/guc: Introduce buffer based cmd transport Michal Wajdeczko
2017-05-26 12:26 ` Chris Wilson
2017-05-26 11:13 ` [CI v4 3/3] HAX Enable GuC loading & submission Michal Wajdeczko
2017-05-26 11:32 ` ✗ Fi.CI.BAT: warning for Introduce buffer based cmd transport (rev3) Patchwork
2017-05-26 12:27 ` Chris Wilson
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=1496132559.3977.3.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.wajdeczko@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 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.