From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Lionel Landwerlin <lionel.g.landwerlin@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/4] drm/i915: expose engine availability through sysfs
Date: Mon, 20 Nov 2017 17:08:16 +0000 [thread overview]
Message-ID: <68e6033c-9094-5dc5-38e2-7a69b147c81b@linux.intel.com> (raw)
In-Reply-To: <8c78e126-457b-1c8e-d9f7-fa1e744a1f58@intel.com>
On 20/11/2017 16:33, Lionel Landwerlin wrote:
> On 20/11/17 16:03, Tvrtko Ursulin wrote:
>> - I would need engine->instance here as well.
> Sure.
> I thought that wasn't uabi though.
Then again engine->instance is already there as the containing directory
name. So do I need it in a separate file, not sure.. so many questions,
so little time.. :)
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-11-20 17:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 12:23 [PATCH 0/4] drm/i915: Expose more GPU properties through sysfs Lionel Landwerlin
2017-11-20 12:23 ` [PATCH 1/4] drm/i915: store all subslice masks Lionel Landwerlin
2017-11-20 12:23 ` [PATCH 2/4] drm/i915/debugfs: reuse max slice/subslices already stored in sseu Lionel Landwerlin
2017-11-20 12:23 ` [PATCH 3/4] drm/i915: expose engine availability through sysfs Lionel Landwerlin
2017-11-20 15:57 ` Tvrtko Ursulin
2017-11-21 12:41 ` Ewelina Musial
2017-11-20 16:03 ` Tvrtko Ursulin
2017-11-20 16:33 ` Lionel Landwerlin
2017-11-20 17:08 ` Tvrtko Ursulin [this message]
2017-11-28 18:17 ` Tvrtko Ursulin
2017-11-28 20:56 ` Chris Wilson
2017-11-28 21:39 ` Chris Wilson
2017-11-29 8:39 ` Tvrtko Ursulin
2017-11-20 12:23 ` [PATCH 4/4] drm/i915: expose EU topology " Lionel Landwerlin
2017-11-20 16:13 ` Tvrtko Ursulin
2017-11-20 16:54 ` Lionel Landwerlin
2017-11-20 12:45 ` ✓ Fi.CI.BAT: success for drm/i915: Expose more GPU properties through sysfs (rev3) Patchwork
2017-11-20 13:33 ` ✓ Fi.CI.IGT: " Patchwork
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=68e6033c-9094-5dc5-38e2-7a69b147c81b@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lionel.g.landwerlin@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