On Sat, 09 Aug 2014, Chris Wilson ch...@chris-wilson.co.uk wrote:
Adapt the macro so that we can pass either the struct drm_device or the
struct drm_i915_private pointers and get the answer we want. Over time,
my plan is to convert all users over to using drm_i915_private and so
trimming down
On Mon, Aug 11, 2014 at 01:14:50PM +0300, Jani Nikula wrote:
On Sat, 09 Aug 2014, Chris Wilson ch...@chris-wilson.co.uk wrote:
Adapt the macro so that we can pass either the struct drm_device or the
struct drm_i915_private pointers and get the answer we want. Over time,
my plan is to
On Mon, Aug 11, 2014 at 11:26:07AM +0100, Chris Wilson wrote:
On Mon, Aug 11, 2014 at 01:14:50PM +0300, Jani Nikula wrote:
On Sat, 09 Aug 2014, Chris Wilson ch...@chris-wilson.co.uk wrote:
Adapt the macro so that we can pass either the struct drm_device or the
struct drm_i915_private
On Mon, Aug 11, 2014 at 01:25:49PM +0200, Daniel Vetter wrote:
On Mon, Aug 11, 2014 at 11:26:07AM +0100, Chris Wilson wrote:
On Mon, Aug 11, 2014 at 01:14:50PM +0300, Jani Nikula wrote:
On Sat, 09 Aug 2014, Chris Wilson ch...@chris-wilson.co.uk wrote:
Adapt the macro so that we can pass
Adapt the macro so that we can pass either the struct drm_device or the
struct drm_i915_private pointers and get the answer we want. Over time,
my plan is to convert all users over to using drm_i915_private and so
trimming down the pointer dance. Having spent a few hours chasing that
goal and
