All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Use drm_i915_private directly from drv_get_drvdata()
Date: Tue, 6 Aug 2019 11:07:10 +0300	[thread overview]
Message-ID: <20190806080710.GA30053@intel.intel> (raw)
In-Reply-To: <20190806074219.11043-1-chris@chris-wilson.co.uk>

Hi Chris,

On Tue, Aug 06, 2019 at 08:42:19AM +0100, Chris Wilson wrote:
> As we store a pointer to i915 in the drvdata field (as the pointer is both
> an alias to the drm_device and drm_i915_private), we can use the stored
> pointer directly as the i915 device.
> 
> v2: Store and use i915 inside drv_get_drvdata()
> v3: Only expect i915 inside drv_get_drvdata() so drop the assumed
> i915/drm equivalence.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Andi Shyti <andi.shyti@intel.com>

Reviewed-by: Andi Shyti <andi.shyti@intel.com>

Thanks,
Andi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-08-06  8:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06  7:42 [PATCH] drm/i915: Use drm_i915_private directly from drv_get_drvdata() Chris Wilson
2019-08-06  8:07 ` Andi Shyti [this message]
2019-08-06  8:32 ` ✓ Fi.CI.BAT: success for drm/i915: Use drm_i915_private directly from drv_get_drvdata() (rev3) Patchwork
2019-08-06 15:34 ` ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2019-07-29 11:04 [PATCH] drm/i915: Use drm_i915_private directly from drv_get_drvdata() Chris Wilson
2019-07-29 14:32 ` Michal Wajdeczko
2019-07-29 14:37   ` Chris Wilson

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=20190806080710.GA30053@intel.intel \
    --to=andi.shyti@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 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.