From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [RFC] drm/i915/guc: Move GuC log related functions into dedicated file
Date: Mon, 16 Jan 2017 08:25:57 +0000 [thread overview]
Message-ID: <d073da95-0c77-3800-55b2-45b657bd086d@linux.intel.com> (raw)
In-Reply-To: <20170113174932.GS28328@nuc-i3427.alporthouse.com>
On 13/01/2017 17:49, Chris Wilson wrote:
> On Fri, Jan 13, 2017 at 05:41:57PM +0000, Michal Wajdeczko wrote:
>> Functions supporting GuC logging capabilities were spread across
>> many files, with unnecessary exposures and mixed with unrelated
>> code. Dedicate file will make maintenance of all GuC functions
>> easier as more functions are coming to support GuC submissions.
>>
>> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>
> Looks clean enough. I don't expect any objections, anyone?
No objections whatsoever, just the opposite!
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-01-16 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 17:41 [RFC] drm/i915/guc: Move GuC log related functions into dedicated file Michal Wajdeczko
2017-01-13 17:49 ` Chris Wilson
2017-01-16 8:25 ` Tvrtko Ursulin [this message]
2017-01-16 9:11 ` Arkadiusz Hiler
2017-01-13 18:23 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-01-18 7:32 ` Tvrtko Ursulin
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=d073da95-0c77-3800-55b2-45b657bd086d@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.wajdeczko@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