From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Zhi Wang <zhi.a.wang@intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Widawsky, Benjamin" <benjamin.widawsky@intel.com>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [RFCv6 2/2] drm/i915: Introduce private PAT management
Date: Thu, 31 Aug 2017 11:25:37 +0300 [thread overview]
Message-ID: <1504167937.5449.2.camel@linux.intel.com> (raw)
In-Reply-To: <9c5674b2-bc85-4765-5d5d-37c0a44f4cff@intel.com>
On Thu, 2017-08-31 at 12:49 +0800, Zhi Wang wrote:
> Hi Vivi:
> Thanks for the reply! The register are written in ppat->update_hw()
> now.
Could we do like I already asked and not simultaneously change the code
organization and register values? Just have this patch write exactly
the same values to all registers than before, then a patch after this
which removes the supposedly unused variables from kernel.
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-08-31 8:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 18:14 [RFCv6 1/2] drm/i915: Factor out setup_private_pat() Zhi Wang
2017-08-29 18:14 ` [RFCv6 2/2] drm/i915: Introduce private PAT management Zhi Wang
2017-08-30 22:00 ` Vivi, Rodrigo
2017-08-31 4:49 ` Zhi Wang
2017-08-31 5:15 ` Rodrigo Vivi
2017-08-31 5:22 ` Wang, Zhi A
2017-08-31 5:24 ` Zhi Wang
2017-08-31 5:47 ` Vivi, Rodrigo
2017-08-31 18:40 ` Wang, Zhi A
2017-08-31 8:25 ` Joonas Lahtinen [this message]
2017-08-31 8:28 ` Wang, Zhi A
2017-08-31 14:20 ` Joonas Lahtinen
2017-08-31 15:37 ` Wang, Zhi A
2017-08-29 18:37 ` ✗ Fi.CI.BAT: failure for series starting with [RFCv6,1/2] drm/i915: Factor out setup_private_pat() 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=1504167937.5449.2.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=benjamin.widawsky@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=zhi.a.wang@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.