From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 2/3] drm/i915/uc: Update drawing for firmware layout
Date: Thu, 25 Jul 2019 21:24:17 +0100 [thread overview]
Message-ID: <156408625703.31349.10937442459154697046@skylake-alporthouse-com> (raw)
In-Reply-To: <8ac751a3-9666-5b82-a298-c4e327a470f2@intel.com>
Quoting Daniele Ceraolo Spurio (2019-07-25 21:16:23)
>
>
> On 7/25/19 7:13 AM, Michal Wajdeczko wrote:
> > Sphinx was rendering firmware layout as html table, but since
> > we want to add sizes relations switch to plain text graphics.
> >
> > v2: also update text and do it before move (Daniele)
> >
> > Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> > Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>
> Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
And pushed, thanks for the fixes and updates.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-07-25 20:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 14:13 [PATCH v2 1/3] drm/i915: Fix GuC documentation links Michal Wajdeczko
2019-07-25 14:13 ` [PATCH v2 2/3] drm/i915/uc: Update drawing for firmware layout Michal Wajdeczko
2019-07-25 20:16 ` Daniele Ceraolo Spurio
2019-07-25 20:24 ` Chris Wilson [this message]
2019-07-25 14:13 ` [PATCH v2 3/3] drm/i915/uc: Move uc firmware layout definitions to dedicated file Michal Wajdeczko
2019-07-25 15:29 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/3] drm/i915: Fix GuC documentation links Patchwork
2019-07-25 16:13 ` ✓ Fi.CI.BAT: success " Patchwork
2019-07-26 5:47 ` ✗ Fi.CI.IGT: failure " 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=156408625703.31349.10937442459154697046@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--cc=daniele.ceraolospurio@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.