public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: "Michael H. Nguyen" <michael.h.nguyen@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/bdw: Initialize workarounds in render ring init fn.
Date: Mon, 25 Aug 2014 23:39:19 +0200	[thread overview]
Message-ID: <20140825213919.GU15520@phenom.ffwll.local> (raw)
In-Reply-To: <53EE9722.5020606@intel.com>

On Fri, Aug 15, 2014 at 04:26:26PM -0700, Michael H. Nguyen wrote:
> Also, should this be defined in a userspace accessible header? I see this
> defined again locally in the IGT test.

It's a debugfs interface, i.e. no real ABI guarantees. And so better not
to expose this in any of the uapi header files. We've done pretty much
the same duplication for all other debugfs files used in igt tests.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2014-08-25 21:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14 16:51 [PATCH] drm/i915/bdw: Initialize workarounds in render ring init fn arun.siluvery
2014-08-15 23:26 ` Michael H. Nguyen
2014-08-25 21:39   ` Daniel Vetter [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=20140825213919.GU15520@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=michael.h.nguyen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox