intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 2/2] drm/i915: split out display debugfs to a separate file
Date: Fri, 14 Feb 2020 13:44:36 +0200	[thread overview]
Message-ID: <87r1yxwfyz.fsf@intel.com> (raw)
In-Reply-To: <158167844647.10420.11414553000061385342@skylake-alporthouse-com>

On Fri, 14 Feb 2020, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Jani Nikula (2020-02-11 16:14:51)
>> The i915_debugfs.c has grown more than a little unwieldy. Split out the
>> display related debugfs code to a file of its own under display/,
>> initialized with a separate call. No functional changes.
>> 
>> v2:
>> - Also moved i915_frontbuffer_tracking, i915_gem_framebuffer,
>>   i915_power_domain_info, i915_dmc_info, i915_ipc_status (Ville)
>> 
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> The diff unnerved me, but I couldn't spot anything other than code motion.
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>

Many thanks, pushed to dinq.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-02-14 11:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 16:14 [Intel-gfx] [PATCH v2 1/2] drm/i915: move intel_csr.[ch] under display/ Jani Nikula
2020-02-11 16:14 ` [Intel-gfx] [PATCH v2 2/2] drm/i915: split out display debugfs to a separate file Jani Nikula
2020-02-14 11:07   ` Chris Wilson
2020-02-14 11:44     ` Jani Nikula [this message]
2020-02-11 16:29 ` [Intel-gfx] [PATCH v2 1/2] drm/i915: move intel_csr.[ch] under display/ Ville Syrjälä
2020-02-11 16:32   ` Chris Wilson
2020-02-14  7:06     ` Jani Nikula
2020-02-11 16:32   ` Jani Nikula
2020-02-13 20:03 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [v2,1/2] " Patchwork
2020-03-02 15:53 ` [Intel-gfx] [PATCH v2 1/2] " Ville Syrjälä

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=87r1yxwfyz.fsf@intel.com \
    --to=jani.nikula@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).