From: akaras <anna.karas@intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/i915/guc: improve documentation
Date: Mon, 7 Oct 2019 14:31:42 +0300 [thread overview]
Message-ID: <20191007113142.GA10831@akaras-dev> (raw)
In-Reply-To: <20190927214243.18558-2-daniele.ceraolospurio@intel.com>
Hello Daniele,
On Fri, Sep 27, 2019 at 02:42:42PM -0700, Daniele Ceraolo Spurio wrote:
> Add a short description of what we expect from GuC and some minor
> improvements to existing documentation. Also remove a comment about a
> difference between GuC and HuC that is not true anymore.
>
> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
Acked-by: Anna Karas <anna.karas@intel.com>
Anna Karas
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-10-07 11:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 21:42 [PATCH 1/3] drm/i915: Add microcontrollers documentation section Daniele Ceraolo Spurio
2019-09-27 21:42 ` [PATCH 2/3] drm/i915/guc: improve documentation Daniele Ceraolo Spurio
2019-10-07 11:31 ` akaras [this message]
2019-10-09 14:35 ` Martin Peres
2019-09-27 21:42 ` [PATCH 3/3] drm/i915/huc: " Daniele Ceraolo Spurio
2019-10-07 11:37 ` Anna Karas
2019-10-09 14:41 ` Martin Peres
2019-10-09 21:44 ` Daniele Ceraolo Spurio
2019-10-09 23:17 ` Daniele Ceraolo Spurio
2019-09-28 0:01 ` ✗ Fi.CI.BAT: failure for series starting with [1/3] drm/i915: Add microcontrollers documentation section Patchwork
2019-10-07 11:04 ` [PATCH 1/3] " root
2019-10-09 14:26 ` Martin Peres
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=20191007113142.GA10831@akaras-dev \
--to=anna.karas@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-gfx@lists.freedesktop.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.