From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/5] drm/i915: Expose __raw_i915_read() & co. to the outside, and a few forcewake things
Date: Mon, 26 Oct 2015 16:46:56 +0200 [thread overview]
Message-ID: <20151026144656.GH26517@intel.com> (raw)
In-Reply-To: <20151022134129.GY2551@nuc-i3427.alporthouse.com>
On Thu, Oct 22, 2015 at 02:41:29PM +0100, Chris Wilson wrote:
> On Thu, Oct 22, 2015 at 03:34:55PM +0300, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > These patches fell off from my type safe register access series. I
> > figured I'd post them separately since they're a fairly separate
> > piece of work.
> >
> > Ville Syrjälä (5):
> > drm/i915: Turn __raw_i915_read8() & co. in to inline functions
> > drm/i915: Read FORCEWAKE registers with I915_READ_FW()
> > drm/i915: Minor style nits in intel_uncore.c
> > drm/i915: Respin vlv/chv reagister access to look more like SKL
> > drm/i915: Add NEEDS_FORCEWAKE() checks for vlv/chv
>
> All Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Entire series merged, with typos corrected. Thanks for the reviews.
>
> We can still replace the vGPU block with just a volatile struct * which
> would remove a few more warts.
> -Chris
>
> --
> Chris Wilson, Intel Open Source Technology Centre
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-10-26 14:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 12:34 [PATCH 0/5] drm/i915: Expose __raw_i915_read() & co. to the outside, and a few forcewake things ville.syrjala
2015-10-22 12:34 ` [PATCH 1/5] drm/i915: Turn __raw_i915_read8() & co. in to inline functions ville.syrjala
2015-10-22 13:32 ` Daniel Vetter
2015-10-22 13:49 ` Ville Syrjälä
2015-10-22 12:34 ` [PATCH 2/5] drm/i915: Read FORCEWAKE registers with I915_READ_FW() ville.syrjala
2015-10-22 13:37 ` Daniel Vetter
2015-10-22 13:50 ` Ville Syrjälä
2015-10-22 12:34 ` [PATCH 3/5] drm/i915: Minor style nits in intel_uncore.c ville.syrjala
2015-10-22 13:38 ` Daniel Vetter
2015-10-22 12:34 ` [PATCH 4/5] drm/i915: Respin vlv/chv reagister access to look more like SKL ville.syrjala
2015-10-22 13:42 ` Daniel Vetter
2015-10-22 12:35 ` [PATCH 5/5] drm/i915: Add NEEDS_FORCEWAKE() checks for vlv/chv ville.syrjala
2015-10-22 13:44 ` Daniel Vetter
2015-10-22 13:41 ` [PATCH 0/5] drm/i915: Expose __raw_i915_read() & co. to the outside, and a few forcewake things Chris Wilson
2015-10-26 14:46 ` Ville Syrjälä [this message]
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=20151026144656.GH26517@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox