From: Chris Wilson <chris@chris-wilson.co.uk>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Use drm_i915_private directly from debugfs
Date: Mon, 10 Apr 2017 12:07:44 +0100 [thread overview]
Message-ID: <20170410110744.GH6834@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1491820966.3364.4.camel@linux.intel.com>
On Mon, Apr 10, 2017 at 01:42:46PM +0300, Joonas Lahtinen wrote:
> On pe, 2017-04-07 at 20:42 +0100, Chris Wilson wrote:
> > The void *data passed to debugfs callbacks is actually the
> > drm_i915_private pointer, so use it thusly and avoid the to_i915(dev)
> > indirection.
> >
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Pushed the trivial patch before drm_device starts making a comeback.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-04-10 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 18:48 [PATCH] drm/i915: Use drm_i915_private directly from debugfs Chris Wilson
2017-04-07 19:08 ` ✗ Fi.CI.BAT: failure for " Patchwork
2017-04-07 19:42 ` [PATCH] " Chris Wilson
2017-04-10 10:42 ` Joonas Lahtinen
2017-04-10 11:07 ` Chris Wilson [this message]
2017-04-07 20:09 ` ✓ Fi.CI.BAT: success for drm/i915: Use drm_i915_private directly from debugfs (rev2) Patchwork
2017-04-08 12:55 ` [PATCH] drm/i915: Use drm_i915_private directly from debugfs kbuild test robot
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=20170410110744.GH6834@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.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.